Delivery of dynamic content based upon predetermined thresholds

ABSTRACT

A method for creating a unique digital experience based upon meeting a predefined threshold of users within a system comprising: detecting a machine-readable code with a user device and determining an identification of a user, the user device, or both; determining whether the identification of the user device contains a unique ID by querying a server; wherein if no unique ID is identified, issuing the unique ID to the user device; storing the unique ID within a database; determining a threshold of users for the system, wherein unique digital coupons are held until the meeting of said threshold; meeting said threshold and generating a unique digital coupon, said digital coupon being unique to the unique ID; and delivering the unique digital coupon to said user device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 63/201,376 filed on Apr. 27, 2021, U.S. ProvisionalPatent Application No. 63/201,373 filed on Apr. 27, 2021, U.S.Provisional Patent Application No. 63/201,374 filed on Apr. 27, 2021,U.S. Provisional Patent Application No. 63/269,015 filed on Mar. 8,2022, and U.S. patent application Ser. No. 17/446,298 filed on Aug. 29,2021, which is a continuation-in-part of U.S. patent application Ser.No. 17/302,233 filed on Apr. 27, 2021, which claims the benefit of U.S.Provisional Patent Application No. 63/015,688 filed on Apr. 27, 2020,all with the United States Patent and Trademark Office, the contents ofwhich are incorporated herein by reference in their entirety.

FIELD OF THE INVENTION

The invention is related to distribution of digital content by accessingthrough a machine-readable code, and wherein content is specificallydistributed upon meeting of a pre-determined threshold.

BACKGROUND OF THE INVENTION

Motion picture trailers and advertising campaigns take considerableresources to produce and launch. Brand owners and stakeholders want toensure that their campaign is viewed by the greatest number of peoplegiving them a return on their investment. Additionally, currenttechnology and social media has made it easy for the average user tocapture that content and leak it to the general public before thestakeholder is ready for the content to be released or an average usercan unofficially disseminate the content on channels not approved by thestakeholder.

Advertising space at highly attended and viewed events such as the SuperBowl and Olympics demand a premium price because there is a guaranteedaudience. However, audiences are consuming vast sums of content fromtheir smart phones and tablets. Therefore, as consumers continue toconsume content in digital format, and increasingly from their handleddevices, it becomes increasingly difficult for advertising campaigns tobe impactful as stakeholders struggle to reach their intended audience.

Applicant has generated a new system and methodologies of generatingcontent to an audience, based on the occurrence of certain triggerswithin the system, which provides for a gamification of the release ofcertain content, based on an individual user's actions or the actions ofthe system community as a whole. Such systems and methods provide fornew and unique mechanisms to generate and release content to the userswithin the system.

SUMMARY OF THE INVENTION

The present invention is a system for delivering content to users onlywhen a predetermined threshold has been met by users on the system. Uponthe occurrence of that predetermined threshold, the system knows thatthere are enough users on the system so that the content will havemaximum impact. The embodiments detailed herein specifically detailsystems and methods for generating content by accessing amachine-readable code (“MRC”). In particular, preferred embodimentsgenerate unique content, and wherein the system utilizes a unique ID toidentify a user device within the system. These advantages allow fornovel and unique opportunities that are not possible in the prior art.The system includes a plurality of tags, each with a MRC, each of theMRCs encoding a unique address and/or identification number that willdirect the user device to a server system.

In one embodiment, the present invention provides a system fordisplaying customized content to users at a venue via a user device. Thesystem comprising a server system having a computer processor and acomputer memory; a plurality of tags, each with a MRC, each of themachine-readable codes encoding an address controlled by the serversystem, each of the tags being operatively mounted within the venue foraccess by the users in the venue. The server system performs thefollowing steps: storing content in a database; collecting user dataassociated with the user; receiving a request from one of the userdevices, the request being generated by scanning one of the tags withthe user device; determining the user data associated with the user whoscanned the tag; selecting, based upon meeting a threshold number ofusers, customized content from the content in the database; anddelivering the customized content to the user device.

In a further preferred embodiment, a system for generating a uniquecontent to a user device comprising: a server system having a computerprocessor and memory; a plurality of tags, each with a MRC, each of theMRCs encoding an address controlled by the server system, each of thetags being operatively mounted within the venue for access by the userdevices in the venue; and wherein the computer memory of the serversystem stores executable code, wherein when executed, enables the serverto perform a process comprising the following steps: receiving a requestfrom one user device, the request generated by scanning one of the tagswith said user device; directing the user device to a tag URL that isuniquely encoded to the tag; receiving at a redirect/identificationserver, the URL request, and determining whether the user device is newor returning, and informing an interface server of the result; theredirect/identification server counting the number of new or returninguser devices to the system; when the total number of unique user devicesreaches a predetermined threshold, receiving an instruction at aninterface server which executes the process described in FIG. 5regarding content to be generated; providing a second URL to theredirect/identification server; sending the second URL to the userdevice; displaying, from said second URL, unique content on said userdevice; obtaining a data from said user device; and upon the occurrenceof a trigger, receiving a new URL from said interface server.

The embodiments detailed herein specifically detail systems and methodsfor generating content by accessing a machine-readable code (“MRC”). Inparticular, preferred embodiments generate unique content, and whereinthe system utilizes a unique ID to identify a user device within thesystem. These advantages allow for novel and unique opportunities thatare not possible in the prior art. With regard to entertainment venues,the present invention provides a system for the display of interactivecontent on a user device based on a number of determining factorsincluding seat location, venue location, past user interactions, as wellas data provided from other sources such as ticketing platform softwareand advertising database portals.

The system includes a plurality of tags, each with a MRC, each of theMRCs encoding a unique tag ID and/or tag URL that will direct the userdevice to a server system. The system may work independently of othermultimedia displays located inside of the venue while providing contentthat is prescheduled or managed off site by the system. In certainembodiments, the system may also orchestrate the displayed user contentbased on the display of the multimedia production on the venuemultimedia display system, when it receives a request from one of theuser devices, generated by scanning one of the unique MRCs and/or NFCenabled tags with the user device, and provides the interactive contentthat corresponds, in real time, with the multimedia production currentlybeing played on the venue multimedia display system.

In one embodiment, the present invention provides a system fordisplaying customized content to users at a venue via a user device. Thesystem comprising a server system having a computer processor and acomputer memory; a plurality of tags, each with a MRC, each of themachine-readable codes encoding an address controlled by the serversystem, each of the tags being operatively mounted within the venue foraccess by the users in the venue. The server system performs thefollowing steps: storing content in a database; collecting user dataassociated with the user; receiving a request from one of the userdevices, the request being generated by scanning one of the tags withthe user device; determining the user data associated with the user whoscanned the tag; selecting, based upon the user data, customized contentfrom the content in the database; and, upon the meeting of a threshold,delivering the customized content to the user device.

A further objective is to provide a system that enables a variety ofinteractions with the venue and the users attending an event at thevenue, for increased entertainment, more effective sales at the venue,and more effective marketing. The objective of these interactions is toprovide users individualized content that is based on multiple datapoints in order for content to be relevant to users on a personal level.Each scan of the uniquely encoded NFC enabled and/or MRC will allow thesystem to provide personalized content to the user, while generatinguser data that can be attributed to a specific user who scanned thattag, or all past users who have scanned a tag specific to a venue orseat and utilized to provide more relevant content during current andfuture use sessions. Furthermore, the personalized content is enabled bycreation of a unique user ID that corresponds specifically to a userdevice, wherein content can thus be specifically tailored and modifiedindependently to each unique user ID, and not simply to all users withinthe system. This allows for the use of user captured data to modify andupdate personalized content in a strategic manner.

Another objective is to provide a system that provides greater level ofcustomization to the content being disseminated. The customizationallows for capture of relevant data from the user device, the location,prior locations of the user device (e.g., as captured by GPS or otherknown locations where a user device accessed an tag in the system),personal information given by a user, browsing habits and other datagathered from the user device, and other third-party API that haverelevant data regarding the user or the user device.

In a further preferred embodiment, a method for delivering uniquecontent to a user device via a MRC, comprising the steps of: detectingthe MRC with the user device and determining an identification of auser, the user device, or both; determining whether the identificationof the user device contains a unique ID stored in a manifest or anyother location on the user device by querying a redirect/identificationserver; wherein if no unique ID is identified, issuing the unique ID tothe user device; determining information about the user based upon theinformation connected to the unique ID and the unique user record;customizing the content to said user based upon the identification ofthe user, the user device, or both; and, upon meeting a thresholdrelated to the particular user collecting data, delivering the contentto the user device; wherein the content comprises a unique contentoffer.

In a further embodiment, the method further comprising: modifying thecontent based upon the occurrence of a trigger.

In a further embodiment, the method further comprising: wherein theunique ID is created by making a determination on if a user and/or userdevice in the redirect/identification server is unique, and if theanswer is “yes,” the interface server will request content from thecontent management software which includes an unissued, unique ID thatis only offered one time to one user.

In a further embodiment, the method further comprising: wherein the MRCis selected from the group consisting of: a bar code, a quick response(QR) code, near field communication (NFC) code, radio frequencyidentification (RFID) code, or combinations thereof. In a furtherembodiment, the method further comprising: wherein the identification ofthe user comprises identification of a data, wherein, upon eachdetection of the MRC, the data is updated. In a further embodiment, themethod further comprising: wherein querying a redirect/identificationserver comprises identification of a data corresponding to the uniqueID.

In a further embodiment, the method further comprising: wherein the datais selected from the group consisting of: a date, a time, a GPS locationof the machine-readable code, a type of communication device used toscan the machine-readable code, an orientation of a communication devicewhen the machine-readable code was scanned, a type of operating systemon a communication device that scanned a tag; and combinations thereof.

In a further embodiment, the method further comprising: wherein thecustomizable content directs the user device to a Web page, and whereinanalytical data from the Web page is collected and consists of the dataselected from the group consisting of: time spent on a Web page,purchases made, IP address, personal information input by the user,products viewed, and combinations thereof. In a further embodiment, themethod further comprising: wherein data is collected and aggregatedevery time a user accesses the redirect/identification server, theinterface server or the tag. In a further embodiment, the method furthercomprising: wherein the step of modifying the content is predeterminedbased on the occurrence of a trigger and stored within a database and isautomatically disseminated upon the occurrence of the trigger.

In a further preferred embodiment, a system for displaying a uniquecontent to users at a venue via a user device, the system comprising: aserver system having a computer processor and memory; a plurality oftags, each with a MRC, each of the MRCs encoding an address controlledby the server system, each of the tags being operatively mounted withinthe venue for access by the user devices in the venue; and wherein thecomputer memory of the server system stores executable code, whereinwhen executed, enables the server to perform a process comprising thefollowing steps: receiving a request from one user device, the requestgenerated by scanning one of the tags with said user device; determiningwhether a manifest with a unique ID is associated with said user deviceor generating a new manifest and assigns it a unique ID to the userdevice that scanned the tag; collecting a user data associated with theuser device, wherein each user device comprises a manifest with a uniqueID; generating a targeted advertisement based upon the total number ofusers to the system; selecting, based upon the user data, the uniquecontent from the content in the database, wherein the customized contentprovides the unique content, wherein said unique content is storedwithin said server; wherein upon the occurrence of the total number ofusers to the system, providing the unique content to the user device;identifying the occurrence of a trigger; and generating a new uniquecontent on said user device based upon the occurrence of the triggerthat is unique to the unique certificate.

In a further embodiment, the system wherein upon each subsequent scan ofthe tag, generating a new unique content within said server for deliveryto the user device. In a further embodiment, the system wherein thecontent is modified based upon an action performed on said user device.In a further embodiment, the system wherein the content is a digitaloffer. In a further embodiment, the system wherein the digital offer ismodified by a provider of said digital offer.

In a further embodiment, the system wherein the trigger is selected fromthe group consisting of: an action in a game, a score in a game, acharitable donation, a purchase, a predetermined time, inventory, orcombinations thereof. In a further embodiment, the system wherein theMRC is printed on a surface. In a further embodiment, the system whereinthe MRC is embedded within a surface. In a further embodiment, thesystem wherein the MRC identifies a specific location via a knownlocation of the MRC, GPS, or both. In a further embodiment, the systemwherein the digital offer is modified based upon sharing of the digitaloffer to at least five additional user devices.

In a further embodiment, the system wherein the customizable contentdirects the user device to a Web page, and wherein analytical data fromthe Web page is collected and consists of the data selected from thegroup consisting of: time spent on a Web page, purchases made, IPaddress, personal information input by the user, products viewed,cookies, pixels, and combinations thereof. In a further embodiment, thesystem wherein the user device further receives in-venue metrics via anin-venue metrics API, and which said in-venue metrics are utilized asdata or to modify the content. In a further embodiment, the systemwherein the user device further receives third-party metrics via athird-party metrics API, and wherein said third-party metrics areutilized as data or to modify the content. In a further embodiment, thesystem ticket brokerage metrics via a ticket brokerage metrics API, andwhich said in-venue metrics are utilized as data or to modify thecontent. In a further embodiment, the system wherein the data includespersonal information added by a user.

In a further embodiment, the system wherein the MRC is located within anLCD/LED/e-ink display device embedded or affixed to seating surface,which can be updated in real time. In a further embodiment, the systemwherein the MRC is displayed upon a video board located within thevenue. In a further embodiment, the system wherein the tag is modifiedby the occurrence of a trigger. In a further embodiment, the systemwherein the trigger is related to an action performed by fan(s) inattendance of an event.

In a further preferred embodiment, a system for generating a uniquecontent to a group of user devices comprising: a server system having acomputer processor and memory; a plurality of tags, each with a MRC,each of the MRCs encoding an address controlled by the server system,each of the tags being operatively mounted within the venue for accessby the user devices in the venue; and wherein the computer memory of theserver system stores executable code, wherein when executed, enables theserver to perform a process comprising the following steps: receiving arequest from one user device, the request generated by scanning one ofthe tags with said user device; directing the user device to a tag URLthat is uniquely encoded to the tag; receiving at aredirect/identification server, the URL request, and determining whetherthe user device is new or returning, and informing an interface serverof the result; generating an unused unique ID for a new user which isstored in a database; receiving an instruction at an interface serverfrom a target determination process regarding content to be generated;querying the system to determine if a threshold data has been met fordeploying the unique content; providing a second URL to the interfaceserver; upon meeting the threshold data, sending the second URL to alluser devices who participated in meeting the threshold data; displaying,from said second URL, unique content on said user devices; obtaining adata from said user devices; and upon the occurrence of a trigger,receiving a new URL from said interface server.

In a further preferred embodiment, a method for creating a uniquedigital offer comprising: detecting a tag with a user device anddetermining an identification of a user, the user device, or both;determining whether the identification of the user device contains amanifest with a unique ID by querying an interface server; wherein if nomanifest with a unique ID is identified, issuing the unique ID to theuser device; storing, within a database, the unique digital offer to begenerated upon the occurrence of a threshold regarding data capture bythe user device or the system as a whole; generating a unique digitaloffer, said digital offer being unique to the unique ID; and, uponmeeting of the threshold, delivering the unique digital offer to saiduser device.

In a further embodiment, a system for generating a unique content to atleast one user device upon meeting a threshold of users to the systemcomprising: a server system having a computer processor and computermemory; a plurality of machine-readable codes, each of themachine-readable codes encoding an address controlled by the serversystem, each of the machine-readable codes being operatively mountedwithin the venue for access by all user devices in the venue; andwherein the computer memory of the server system stores executable code,wherein when executed the executable code enables the server to performa process comprising the following steps: (i) receiving a request fromone user device, the request generated by scanning one of themachine-readable codes with said user device; (ii) directing the userdevice to a tag URL that is uniquely encoded to the machine-readablecode; (iii) receiving at a redirect/identification server the tag URLrequest, determining a result of whether the at least one user device isnew or returning, and informing an interface server of the result; (iv)generating manifest and an unused unique ID for a new user which isstored in a database; (v) receiving an instruction at the interfaceserver from a target determination process regarding mobile content tobe generated upon the meeting of the threshold; (vi) providing a secondURL to the redirect/identification server; (vii) sending the second URLto the at least one user device; (viii) displaying from said second URLunique content on said at least one user device; (ix) obtaining a datafrom said at least one user device; and (x) upon an occurrence of atrigger, receiving a new URL from said content management server.

In a further embodiment, a method for creating a unique digitalexperience based upon meeting a pre-defined threshold of users within asystem, comprising: detecting a machine-readable code with a user deviceand determining an identification of a user, the user device, or both;determining whether the identification of the user device contains amanifest with a unique ID by querying a redirect/identification server;wherein if no manifest with a unique ID is identified, issuing themanifest with a unique ID to the user device; storing within a databasethe unique ID; determining a threshold of users for the system, whereinunique digital offers are held until the meeting of said threshold;meeting said threshold and generating a unique digital offer, saiddigital offer being unique to the unique ID; and delivering the uniquedigital offer to said user device.

In a further embodiment, a system for displaying a unique content tousers at a venue via at least one user device, the system comprising: aserver system having a computer processor and computer memory; aplurality of machine-readable codes, each of the machine-readable codesencoding an address controlled by the server system, each of themachine-readable codes being operatively mounted within the venue foraccess by all user devices in the venue; and wherein the computer memoryof the server system stores executable code, wherein when executed theexecutable code enables the server to perform a process comprising thefollowing steps: (i) receiving a request from one user device, therequest generated by scanning one of the machine-readable codes withsaid user device; (ii) determining whether a manifest with a unique IDis associated with said user device or generating a new unique ID to theuser device that scanned the machine-readable code; (iii) collecting auser data associated with the user device wherein each user devicecomprises a unique ID; (iv) selecting, based upon the user data, theunique content from content in the database, wherein the contentprovides the unique content, wherein said unique content is storedwithin said server; (v) Setting a threshold for delivery of uniquecontent upon meeting the threshold; (vi) providing the unique content tothe user device upon the meeting of the threshold; (vii) identifying atrigger; and (viii) generating a new unique content on said user devicebased upon the trigger that is unique to the unique ID.

In a further embodiment, a method for delivering unique content to auser device via a machine-readable code comprising the steps of:detecting the machine-readable code with the user device and determiningthe identification of a user, the user device, or both; determiningwhether the identification of the user device contains a manifest with aunique ID by querying a redirect/identification server, wherein, if nomanifest with a unique is identified, issuing the unique ID to the userdevice; determining information about the user based upon theinformation connected to the unique ID stored in the manifest;customizing the unique content to be delivered to said user based uponthe identification of the user, the user device, or both; setting athreshold for delivering unique content, and upon meeting the threshold,delivering the unique content to the user device, wherein the uniquecontent comprises a unique mobile content offer.

Other features and advantages of the present invention will becomeapparent from the following more detailed description, taken inconjunction with the accompanying drawings, which illustrate, by way ofexample, the principles of the invention.

In a preferred embodiment, a method for delivering dynamic content to auser device via a machine-readable code comprising: (a) in response toscanning a tag (16 a) comprising the machine-readable code, receiving arequest from a user device (14 a) and detecting the presence of amanifest comprising a unique ID, wherein if no unique ID is present,creating a unique ID and associating a record with the unique ID withina database; (b) detecting from the tag (16 a) a tag ID and determining:(i) whether a venue exists corresponding to the tag ID; and (ii) whetheran event is in progress corresponding to the tag ID; (c) redirecting toa global default target if no venue exists or no event is in progress,and determining if a tag ID is grouped where the venue exists and anevent is in progress; (d) counting, via a counting mechanism, the totalnumber of unique IDs scanning a tag within the venue and determining,via the counting mechanism, whether a threshold number of unique IDshave scanned a tag; (e) upon meeting the threshold number, in responseto the detecting from the tag ID, obtaining tag ID group information andassociating the tag ID with the unique ID; and (f) associating theunique ID and a unique ID record with the tag ID and redirecting a userto an appropriate target.

In a further embodiment, the method further comprising: (d2) providing afirst target to the user device when the threshold number is unmet andredirecting to the target upon meeting the threshold number.

In a further embodiment, the method wherein the threshold number isselected from the group consisting of: a total number of unique users ona system at a time t, the total number of unique users accessing asystem after a time t, x number of scans corresponding to a unique IDand x number of tags, and combinations thereof. In a further embodiment,the method wherein the total number of unique users on the system at atime t is greater than 1,000. In a further embodiment, the methodwherein the total number of unique users on the system after a time t isgreater than 1,000.

In a further embodiment, the method wherein redirecting the user deviceto a new target is redirected through a push notification.

In a further embodiment, the method wherein the machine-readable code isselected from the group consisting of: a barcode, a quick response (QR)code, a near-field communication (NFC) code, a radio-frequencyidentification (RFID) code, and combinations thereof.

In a further embodiment, the method wherein the target is stored withina database and is automatically redirected upon the occurrence of theevent. In a further embodiment, the method wherein the target isselected from the group consisting of: a digital offer and anadvertisement.

In a preferred embodiment, a system for displaying unique content tousers at a venue via at least one user device, the system comprising:(a) a server system having a computer processor and computer memory; (b)a plurality of machine-readable codes, each of the machine-readablecodes encoding an address controlled by the server system, each of themachine-readable codes being operatively mounted within the venue foraccess by all user devices in the venue; (c) a counting mechanismoperably connected to said server system; and (d) wherein the computermemory of the server system stores executable code, wherein whenexecuted the executable code enables the server system to perform aprocess comprising the following steps: (i) receiving a request from oneuser device, the request generated by scanning one of themachine-readable codes with said user device; (ii) determining whether aunique ID is associated with said user device or generating a new uniqueID to the user device that scanned the machine-readable code andassociating said unique ID to a database record; (iii) collecting userdata associated with the user device and storing the same within thedatabase record, wherein each user device comprises a unique ID; (iv)setting a threshold for delivery of unique content upon meeting saidthreshold, said threshold determined by the counting mechanism; and (v)providing the unique content to the user device upon meeting thethreshold.

In a further embodiment, the system wherein the threshold is selectedfrom the group consisting of: a total number of unique users on thesystem at a time t, a total number of users accessing the system after atime t, and combinations thereof.

In a further embodiment, the system wherein upon each subsequent scan ofthe machine-readable code a new unique content is generated within saidserver system for delivery to the user device.

In a further embodiment, the system wherein the unique content is adigital offer or an advertisement. In a further embodiment, the systemwherein the digital offer is modified by a provider of said digitaloffer. In a further embodiment, the system wherein a digital offer isprovided based upon meeting the threshold and wherein said digital offermay be modified based upon meeting a subsequent threshold.

In a further embodiment, the system wherein the threshold is selectedfrom the group consisting of: an action in a game, a score in a game, acharitable donation, a purchase, a predetermined time, inventory, andcombinations thereof.

In a further embodiment, the system wherein the machine-readable code isprinted on a surface.

In a further embodiment, the system wherein the machine-readable code isembedded within a surface.

In a further embodiment, the system wherein the machine-readable codeidentifies a specific location via a known location of themachine-readable code, GPS, or both.

In a further embodiment, the system wherein the user data is selectedfrom the group consisting of: a date, a time, a GPS location of themachine-readable code, a type of communication device used to scan themachine-readable code, an orientation of a communication device when themachine-readable code was scanned, a type of operating system on acommunication device that scanned an interactive code, and combinationsthereof.

In a further embodiment, the system wherein the unique content directsthe user device to a Web page, and wherein analytical data from the Webpage is collected and consists of data selected from the groupconsisting of: time spent on a Web page, purchases made, IP address,personal information input by a user, products viewed, cookies, pixels,and combinations thereof.

In a further embodiment, the system wherein the user device furtherreceives in-venue metrics via an in-venue metrics API and wherein saidin-venue metrics are utilized as data or to modify the unique content.In a further embodiment, the system wherein the user device furtherreceives third party metrics via a third party metrics API, and whereinsaid third party metrics are utilized as data or to modify the uniquecontent. In a further embodiment, the system wherein the user devicefurther receives ticket brokerage metrics via a ticket brokerage metricsAPI, and which said ticket brokerage metrics are utilized as data or tomodify the unique content.

In a further embodiment, the system wherein the user data includespersonal information added by a user.

In a further embodiment, the system wherein the machine-readable code islocated within an LCD/LED/e-ink display device embedded within oraffixed to a surface.

In a further embodiment, the system wherein the machine-readable code isdisplayed upon a video board located within the venue.

In a further embodiment, the system wherein the machine-readable code isdisplayed within an LCD/LED/e-ink display which can be updated in realtime.

In a further embodiment, the system wherein an event is related to anaction performed by fan(s) in attendance of a game.

In a further embodiment, the system wherein the machine-readable code ismodified by the occurrence of an event.

In a preferred embodiment, a system for generating unique content to atleast one user device upon meeting a threshold of users to the systemcomprising: (a) a server system having a computer processor and computermemory; (b) a plurality of machine-readable codes, each of themachine-readable codes encoding an address controlled by the serversystem, each of the machine-readable codes being operatively mountedwithin a venue for access by all user devices in the venue; and (c)wherein the computer memory of the server system stores executable code,wherein when executed the executable code enables the server system toperform a process comprising the following steps: (i) receiving arequest from one user device, the request generated by scanning one ofthe machine-readable codes with said user device; (ii) directing theuser device to a URL that is uniquely encoded to the machine-readablecode; (iii) receiving the request at an identification server,determining a result of whether the at least one user device is new orreturning, and informing an interface server of the result; (iv)generating an unused unique ID for a new user which is stored in adatabase; (v) receiving an instruction at the interface server from atarget determination process regarding digital content to be generatedupon meeting the threshold; (vi) providing a second URL to theidentification server; (vii) sending the second URL to the at least oneuser device; (viii) displaying, from said second URL, unique digitalcontent on said at least one user device; (ix) obtaining a data fromsaid at least one user device; and (x) upon an occurrence of a trigger,receiving a new URL from said interface server.

In a preferred embodiment, a method for distributing dynamic content toa user upon meeting a predefined threshold comprising: (a) detecting amachine-readable code with a user device and determining anidentification of a user, the user device, or both; (b) determiningwhether the identification of the user device contains a unique ID byquerying a server to determine the presence of a unique ID; wherein ifno unique ID is identified, issuing the unique ID to the user device;(c) storing within a database a record associated with said unique ID;(d) determining a threshold, wherein the threshold is defined as apredetermined number of users for a system, wherein upon meeting thethreshold, a digital offer is distributed; (e) meeting said thresholdand generating the digital offer to be redirected or pushed to the userdevice; and (f) delivering the digital offer to said user device.

In a further embodiment, the method wherein the digital offer is uniqueto the unique ID.

In a further embodiment, the method wherein the threshold is at least1,000 users.

In a further embodiment, the method wherein the threshold is at least1,000 users within a geofence.

In a further embodiment, the method wherein the threshold is at least10,000 users, wherein at least 1,000 users are defined within a firstgeofence. In a further embodiment, the method wherein the thresholdfurther includes at least x points scored by a team within a game, saidgame being played within the first geofence.

In a preferred embodiment, a method for distributing dynamic content toa user upon meeting a predefined threshold comprising: (a) detecting amachine-readable code with a user device and determining anidentification of a user, the user device, or both; (b) determiningwhether the identification of the user device contains a unique ID byquerying a server to determine the presence of a unique ID; wherein ifno unique ID is identified, issuing the unique ID to the user device;(c) storing within a database a record associated with said unique ID;(d) determining a threshold, said threshold comprising scanning of apredetermined number of tags by the user device; (e) meeting saidthreshold and generating a digital offer to be redirected or pushed tothe user device; and (f) delivering the digital offer to said userdevice.

In a further embodiment, the method wherein the predetermined number oftags is greater than 10.

In a further embodiment, the method wherein the predetermined number oftags is present within one geofence. In a further embodiment, the methodwherein the predetermined number of tags is provided via a scavengerhunt, wherein the tags to be scanned are populated within a GUI on theuser device.

In a further embodiment, the method wherein the predetermined number oftags comprise scanning of x number of tags dynamically generated on adigital screen during an event, wherein each of said tags dynamicallygenerated on a digital screen is displayed for a finite amount of time.

In a further embodiment, the method wherein a user is directed to afirst target and upon meeting the threshold is directed to a secondtarget, said second target delivering a digital offer.

In a preferred embodiment, a method of delivering dynamic content to aplurality of users comprising: (a) scanning, within a system, a tag by aplurality of user devices, said system comprising at least one tag, aserver, and a database; (b) counting, via a counting mechanism, thetotal number of users having scanned a tag within a defined parameterselected from the group consisting of: a time parameter, a geofenceparameter, and combinations thereof; (c) wherein the counting mechanismcounts only users that are active on the system; and (d) upon athreshold of users being counted by the counting mechanism, providing adigital offer to all users having been counted via the countingmechanism.

In a further embodiment, the method wherein the total number of users isat least 1,000 users active on the system; and wherein the timeparameter defines a window of one hour to receive the 1,000 scans. In afurther embodiment, the method wherein the geofence parameter is definedas a single venue being defined by a geofence. In a further embodiment,the method wherein the geofence parameter is defined by all venues, thenhosing an event. In a further embodiment, the method wherein thegeofence parameter is defined as all users not within a venue.

In a preferred embodiment, a method of delivering dynamic content to aplurality of users comprising: (a) scanning a tag by a plurality ofusers; (b) counting, via a counting mechanism, a total number of usershaving scanned a tag within a defined parameter; (c) wherein thecounting mechanism counts all users scanning any tag within a systemwithin a time threshold; and (d) upon a threshold of users beingcounting by the counting mechanism, providing a digital offer to allusers having been counted via the counting mechanism.

In a further embodiment, the method wherein the total number of users isat least 1,000 users active on the system; and wherein the parameter isa time parameter and wherein the time parameter defines a window of onehour to receive the 1,000 scans.

In a further embodiment, the method wherein the parameter is a geofenceparameter and wherein the geofence parameter is defined as a singlevenue being defined by a geofence. In a further embodiment, the methodwherein the geofence parameter is defined by all venues then hosing anevent. In a further embodiment, the method wherein the geofenceparameter is defined as all users not within a venue.

In a preferred embodiment, a method of delivering dynamic content to auser comprising: (a) scanning a plurality of tags by an individual userdevice; (b) defining a rule, wherein the individual user device scans xnumber of tags within a defined parameter; (c) upon scanning of a firstand nth tag by the individual user device, updating a database toidentify the first and nth tags being scanned; and (d) upon meeting therule by meeting the x number of tags scanned within the definedparameter, delivering the dynamic content.

In a preferred embodiment, a method of delivering dynamic content to atleast one user comprising: (a) scanning a tag within a system; (b)defining a rule, wherein dynamic content shall be delivered upon theoccurrence of a trigger; (c) directing the user to a first target; and(d) redirecting the user to a second target, being the dynamic contentupon the occurrence of the trigger.

In a preferred embodiment, a system for delivering dynamic content to atleast one user comprising: (a) a server system comprising at least oneserver, at least one database, and at least one tag, said tag comprisinga tag ID, said tag ID being a unique identifier of said tag; (b)defining a rule on said system, wherein dynamic content is delivered tothe at least one user; (c) the dynamic content being stored on saiddatabase; and (d) a counting mechanism suitable to count the at leastone user within the system; wherein the system performs the followingsteps: (i) receiving, via a tag, a unique ID from a user device; (ii)defining a time of scanning the tag; (iii) determining a geofencelocation of the user device at the time of scanning the tag; (iv)updating the counting mechanism to identify the number of users activeon the system having scanned a tag; and (v) deploying dynamic content toall users being defined as on the system within the counting mechanism.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts an embodiment of a system for user device generatedinteractions with a system and platform for accessing and viewingtargets, such as content and digital offers.

FIG. 2 depicts a stadium comprising a plurality of video cameras and auser device that is accessing a user portal including access to contentsuch as video, augmented video playback, and digital offers.

FIG. 3 depicts an embodiment of a system for accessing targetinformation from a user device from within a venue or outside of a venueand various back-end platforms for implementing certain targetinformation or for delivering content to the user device.

FIG. 4 depicts an embodiment of a system for identifying and usinginformation particular to a user device and/or to a tag for directingthe user device to an appropriate target.

FIG. 5 depicts an embodiment of a system wherein the system is enabledto push or pull data or information or due to triggering events or rulesto modify or augment a target delivered to a user device.

FIG. 6 is a diagram of one embodiment of a system that enables deliveryof the customized content.

FIG. 7 is a flowchart illustrating the operation of the system of FIG.6.

FIG. 8 is a diagram illustrating a further embodiment of the system.

FIG. 9 is a diagram illustrating a variation of an embodiment of thesystem.

FIG. 10 is a flowchart illustrating the operations of the system of FIG.9.

FIG. 11 depicts an area comprising a plurality of tags positioned atmultiple locations.

DETAILED DESCRIPTION OF THE INVENTION

Various embodiments are described more fully hereinafter with referenceto the accompanying drawings, which form a part hereof, and which show,by way of illustration, specific exemplary embodiments by which theinnovations may be practiced. The embodiments may, however, be embodiedin many different forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope of the embodiments to those skilled in the art. Amongother things, the various embodiments may be methods, systems, media,devices, or any similar or equivalent arrangements known to thoseskilled in the art. Accordingly, the various embodiments may take theform of an entirely hardware embodiment, an entirely software embodimentor an embodiment combining software and hardware aspects. The followingdetailed description is, therefore, not to be taken in a limiting sense.

The embodiments detailed herein and as depicted in the drawing figuresillustrate several embodiments of the invention, which is directed to amethod and system for generating unique content to a plurality of usersbased upon meeting a threshold requirement upon the system. A thresholdrequirement here typically requires some rule or metric to be met, oftena plurality of users, a plurality of accesses to a tag, whether done bya plurality of users and user devices or a single user device. Theunique content provided to the users can then be further modified, as itis unique to each user, wherein the system contains the ability to alterprovided unique content based on data collected from user(s) input andother factors such as third-party data in real time. Content shall meanany content generated by the system and delivered via a URL, Web app, orother feature as detailed herein, to the user device, or to a digitalwallet. The content may be visual content, a replay, an advertisement,or it may be a coupon or a redemption code or something of value, asnon-limiting examples.

As used herein, the below terms will have the following meanings as maybe supplemented elsewhere in this specification:

As used in this application, the words “a,” “an,” and “one” are definedto include one or more of the referenced items unless specificallystated otherwise. The terms “approximately” and “about” are defined tomean±10%, unless otherwise stated. Also, the terms “have,” “include,”“contain,” and similar terms are defined to mean “comprising” unlessspecifically stated otherwise. Furthermore, the terminology used in thespecification provided above is hereby defined to include similar and/orequivalent terms, and/or alternative embodiments that would beconsidered obvious to one skilled in the art given the teachings of thepresent patent application.

ADDRESS: Code used to direct a user device, browser, Web app,progressive Web app, administrator device, server, database, API, tool,software, etc., to a resource within the system or a network.Non-limiting examples of addresses include a uniform resource identifier(URI) or a uniform resource locator (URL).

ADMINISTRATOR: The individual or group of individuals with the abilityto control and set rules and parameters within the system. This could bea third-party administrator, the proprietor, the venue, the owner of thetags, the team or performer participating in the event, a designatedemployee of any of the foregoing, etc.

ADMINISTRATOR DEVICE: Any type of mobile or non-mobile processing devicesuch as a desktop computer, handheld computer (e.g., phone, smartphone,tablet, personal digital assistant), wearable computer (e.g., smartwatch, smart glasses), portable computers (e.g., laptop, netbooks,Chromebook), or wearable or implantable device, and the like usingwireless communication, a camera or other connectivity element that isaccessible only to an administrator or proprietor or an employeedesignated by the administrator or proprietor.

ANALYTICS OR ANALYTICAL DATA: Data collected by the system or retrievedby the system via an API call to an external server or database.Non-limiting examples of analytical data include date, time, GPSlocation, personal identifying information, etc.

APPLICATION PROGRAMMING INTERFACE (“API”): An application programminginterface or programming code that enables data transmission within thesystem, between the system's server and an external server or betweenone software product and another. Non-limiting examples of APIconnections to the system may be third-party vendor databases such asticketing sales platforms, e-commerce sites such as merchandise sales,social media sites, or any other third-party software product that makestheir API available for use by others.

API CALL—Computer code used by the system software to access data,server software or other applications within the system or external tothe system, acting as an intermediary between any two devices or serversthat want to connect with each other for a specified task. As usedherein, API can mean (i) representational state transfer or Rest(RESTful) API; (ii) Simple Object Access Protocol (“SOAP”) API; (iii)extensible markup language-Remote Procedure Calls (“XML-RPC”); (iv) JSONRemote Procedure Calls (“JSON-RPC), (v) open API; (vi) partner API;(viii) internal or private API; (ix) composite API; or (x) any other APIthat is generally known, or will be come to be known in the art. Thus,the system frequently uses an API, or sends an API request, to aninternal or external program, server or database to deliver requestedinformation.

BLOCKCHAIN: Any digitally distributed, decentralized, public or privateledger that exists across a network such as those offered by theproviders including but not limited to Ethereum, Binance Smart Chain,Polkadot, Flow by Dapper Labs, EOS, Tron, Tezos, WAX, Theta, etc.

BROWSER APPLICATION: An application that runs within the Web browser ofa User Device or Computer. The instructions or executable code,typically written in a combination of HTML and JavaScript, is embeddedwithin the Web page that is downloaded from a Web site.

COMPUTER: May be any type of computer such as a laptop computer, desktopcomputer, tablet, and the like, and includes the appropriate hardware,firmware, and software to enable the computer to function as intended.

CONTENT: Any type of information, images, videos, etc. Non-limitingexamples of content can be a video file, an image file, text, executablecode, a digital offer, a digital coupon, a digital wallet offer, an AR,VR or mixed reality filter, a game, a poll, an app, an NFT, etc. Contentcan be specifically formatted for optimal viewing on a user device.

CRYPTO CURRENCY: Any digital currency in which transactions are verifiedand records maintained on a distributed ledger such as blockchain, forexample, Bitcoin, Ethereum, Cardano, Binance Coin, Tether, Solana, XRP,Dodgecoin, etc.

DATABASE MANAGEMENT SYSTEM: A software package designed to define,manipulate, retrieve and manage data in a database, or any othergenerally accepted definition known to those skilled in the art.

DIGITAL OFFER: Any incentive or reward, for example an incentive topurchase at a discounted price or a free giveaway, offered by aproprietor and delivered to users from a server to a user device througha variety of channels. A Digital offer can be code stored in the user'sdigital wallet, a MRC displayed in Web browser and presented to aproprietor for redemption, an e-mail with a unique redemption code, atext message, SMS/MMS, push notification or socket notification with aunique redemption code. Digital offers can be stored anywhere on a userdevice or can be downloaded or turned into physical offers by printing.Digital offers can be limited to a particular user, or a user may sharethe digital offer to other users. If a digital offer is shared, the sameoffer can be shared to multiple other users, or the digital offer can bemodified by the system when it is shared. Digital offers can also beassociated with a unique code that is stored in a database on a serverinternal or external to the system.

DIGITAL WALLET: A software-based system that securely stores users'information such as payment information, passwords, digitalcertificates, digital coupons, crypto currency, tokens, NFTs, digital IDsuch as a digital driver's license or passport, etc. A digital walletcan be a blockchain or crypto currency wallet. A digital wallet can bestored locally on any user device or can be cloud based and accessed bya user device. Digital wallet can also mean digital storage in generalon any user device or computer. Digital wallet can also be referred toas a mobile wallet.

DISTRIBUTED DATABASE SYSTEM: Any database that consists of two or morefiles located in different sites either on the same network or onentirely different networks.

DISTRIBUTED LEDGER: Any database that is consensually shared andsynchronized across multiple sites, institutions, or geographies,accessible by multiple people.

DATA SERVER OR SERVER: Any form of electronic device or plurality ofdevices having at least one computer processor, e.g., a centralprocessing unit (CPU), and some form of computer memory having acapability to store data, as is well known in the art. The server maycomprise hardware, software, and firmware for receiving, storing, and/orprocessing data as described below. The hardware may be in a singleunit, or operably connected via a network. For example, a computer orserver may comprise any of a wide range of digital electronic devices,including, but not limited to, a server, a desktop computer, a laptop, asmart phone, a tablet, a smart watch, smart glasses, a wearable deviceor an implantable device or any form of electronic device capable offunctioning as described herein.

DYNAMIC ELEMENT: An element that is updated, altered, customized, etc.,in response to a change in the status of a metric, trigger, or any otherdatapoint as determined by the system. A non-limiting example of adynamic element is the score of a game. If a goal is completed, then thescore is updated to reflect this change.

EVENT: Non-limiting examples of an event include a professional, amateuror intramural sporting events (i.e., football, baseball, hockey,basketball, soccer, rugby or cricket game, tennis or golf match, trackand field or figure skating event or automobile race), a theatricalperformance (play, musical or opera), a musical concert, elementaryschool, middle school, high school, college or university event, aservice or ceremony (i.e., religious or worship), a tradeshow orconference, guided or self-guided tours (museums, galleries andhistorical site), time spent in a venue such as a visit to a zoo oramusement park, etc.

FAN PORTAL: A GUI, such as a homepage, displayed in the browser of auser device that provides links or access to other pages/modules viabuttons or other means of selecting options from a menu of choices. Thefan portal can also be used for viewing content and receiving digitaloffers.

INTERFACE SERVER: Within the system, a program, executable code or APIstored on a physical server, cloud storage system or in a serverlessenvironment such as Amazon Web Services, which is capable ofcommunicating with other servers, databases and API's internal orexternal to the system. The interface server is able to make and receivecalls, request and receive data, or execute other functions withinsystems. The interface server is also capable of running AI and/orutilizing machine learning.

GEOFENCE: A virtual perimeter for a real-world geographic area or anarea in or around a venue.

GUI OR GRAPHICAL USER INTERFACE: A graphical interface to enableinteractions between a user and the user's device, such as but notlimited to an interface to the Web app.

JUMBO SCREEN: Any display within a venue visible to users attending anevent at a venue. The jumbo screen can be one display or multipledisplays within the venue that can be controlled by the venue. Jumboscreen may also be known as a jumbotron.

LOCATION: An area whose perimeter or parameters are defined in anabstract way without boundaries that are clearly visible to users orproprietors. Non-limiting examples of a location include a town, city,state, country, region, continent, time zone, or geofenced area.

MACHINE-READABLE CODE (“MRC”): A barcode, a quick response (QR) code,near-field communication (NFC) code, radio-frequency identification(RFID) code, universal product code (UPC), machine readable graphics(e.g., having a pattern, matrix, or the like) coding, instructions codedon a chip, or combinations thereof. A MRC may be may be included into(i) a tag that is mounted to a surface, (ii) identification badges suchas, for example, student identification badges, employmentidentification badges, concert badges, and the like, (iii) merchandisesuch as t-shirts, sweatshirts, hats, mugs, glasses, posters, CD's, andthe like, (iv) a piece of paper, cardstock, or plastic that is handed tousers, (v) a video stream viewed over the internet or network televisionchannel, (vi) an LCD/LED/e ink display device embedded, attached oraffixed to a surface.

MANIFEST: A file containing metadata for a group of accompanying filesthat are part of the system that instruct the user device how to handlethe system when it is started.

MINTING: Uniquely publishing a token on the blockchain to make itpurchasable, salable, or tradeable.

NON-FUNGIBLE TOKEN (“NFT”): A non-interchangeable unit of data stored ona digital ledger, such as but not limited to blockchain, that can bepurchased, sold, auctioned, and traded. As used herein, NFT includes thecontract and subject matter associated with the NFT and can also meansemi-fungible token or fractional NFT. Non-limiting examples of thesmart contracts that could govern a NFT include (i) 1/1 NFTs—known asERC-721 tokens on Ethereum and Polygon, KIP17 on the Klatyn blockchain;(ii) Semi-fungible NFTs—known as ERC-1155 tokens on Ethereum andPolygon, KIP37 on Klatyn.

NFT MARKETPLACE: A platform where NFTs can be stored, displayed, bought,sold, traded, auctioned and in some cases minted.

PROPRIETOR: Any person or entity who purchases, subscribes to, orotherwise uses the system and/or platform and who is not a user. AProprietor may or may not have administrative privileges to the system.Non-limiting examples of proprietors include, venue owners, eventpromoters, teams, performers, theatre troupes, religious organizations,educational institutions (i.e., elementary school, middle school, highschool, college, university), restaurants, bars, retail establishments,amusement parks, museums, art galleries, advertisers, media outlets(i.e., network television, cable television, radio, internetbroadcasts), hospitals and health care systems, ticketing platforms,airlines, ride share services, etc.

PROPRIETOR PORTAL: An access point for a proprietor to enter the systemand/or platform typically displayed in a browser.

RECORD: Information that is stored in an electronic or other intangiblemedium without limitations on how the data is structured.

REDIRECT/IDENTIFICATION SERVER: The server within the system that makesa determination on if a user and/or user device that has entered thesystem is unique, by locating the manifest stored on a user device andif a manifest exists, associating the unique ID stored in the manifeston the user device with the database of known unique ID's stored on theredirect/identification server, or for confirming other data based onone or more requests to the redirect/identification server.

REDIRECT URL: An address generated by a server, such as theredirect/identification server or the interface server, in response toan incoming request that points the browser on a user device to adifferent target.

RESOURCE RECORD: A database record associated with a tag ID.

REQUEST: A message sent by one device to another (e.g., phone to server,server to server, computer to server, server to database, etc.) using anaddress to send the request. For example, upon selecting from theoptions available in the Web browser, the selection is coded into arequest that the Web browser sends to the server via an address. Therequest typically provides instructions to the server. Non-limitingexamples of a request can be—GET, POST, PUT, DELETE, CONNECT, OPTIONS.

RULE: A set of conditional statements that tells the system how to reactto a particular situation. Rules can be preprogrammed into the system orcan be set or changed by an administrator or proprietor.

SYSTEM: The network, tags, digital seat platform, etc.

TAG: A physical (e.g., tangible) form, a digital (e.g.,virtual/intangible) form, or may be combinations of both forms thatcontains an MRC. Physical versions of tags may be constructed fromdiverse types of materials. The MRC may be printed, etched, orfabricated onto the tag materials such as paper, glass, plastic, metal,fabric, and the like as a few nonlimiting examples. In the case of tagsthat contain MRC's that are NFC or RFID, the tags may be adhered to,attached to, embedded in, or fabricated on (or combinations thereof) anatural or manmade material such as metal (e.g., aluminum, stainlesssteel), wood, polymer (e.g., plastic), film, glass, and combinationsthereof. The material may then be incorporated into or affixed (e.g.,adhesive or other form of attachment) to an object or location. A tagmay be printed on a single or multiple use badge or ticket. Digital tagsmay include LED/LCD screens or a designated location within a videostream in which the MRC is located.

TAG ID: A unique identifier for the MRC affixed to the tag. The uniqueidentifier can be any combination of letters, numbers, and symbols. Thetag ID is stored in a database on a server and is coded with informationspecific to the location of the tag. For example, the tag ID mightgenerally identify the geographic location of the tag (i.e., the UnitedStates, Pa. and/or Philadelphia), the general venue location of the tag(i.e., Fenway Park, Madison Square Garden, Carnegie Hall, The NaturalHistory Museum), the specific location of the tag within the venue(i.e., Section A, Row 1, Seat 10, next to Van Gogh's “Starry Night”), orany combination of information.

TAG URL: A unique address assigned to the MRC on each tag that mayoptionally include the tag ID.

TARGET: A Web page, file, address, GUI, Web app, progressive Web app,portal, content or digital offer delivered to a user device. Thoseskilled in the art may also refer to a target as an endpoint.

TARGET DETERMINATION PROCESS: The process described in FIG. 5.

TARGET ID: A unique identifier for the Target. The unique identifier canbe any combination of letters, numbers and/or symbols that can be storedin a database, on a server, and/or both. The target ID allows theplatform to distinguish one target from another.

TICKETING PLATFORM: Both the primary ticketing platform and thesecondary ticketing platform.

TRIGGER: The magnitude or condition that must be reached for a certainresult to materialize. Triggers can be determined either by the system,an administrator or a proprietor. Non-limiting examples of a trigger canbe the start or end of an event, something of significance that occursduring the event (i.e., the 10th goal scored, the first encore by amusical act), a single user completing a certain task, or N-number ofusers completing a task.

TOKEN: A digital asset that is stored securely on the blockchain,representing a tradeable asset.

TOOLS: Cookies, pixels, widgets, plug-ins, etc.

UNIQUE ID: A unique identifier for the user device. The uniqueidentifier can be any combination of letters, numbers and/or symbols,cookies, digital credentials or it can be a digital certificate such asTLS, SSL, code signing certificate, client certificate, etc. . . . . Theunique ID can be stored on the user device in any location on the userdevice such as the manifest, local storage or digital wallet, in adatabase on a server, and/or both, and is used to associate the userdevice with the unique user record stored in a database on a server inthe system.

UNIQUE IDENTIFYING INFORMATION: Personal information and demographicscollected about a particular user's such as name, address, phone number,e-mail address, credit card information, gender, marital status,academic affiliation (student, faculty, alumni), driver's licensenumber, age, username, password, pin number, social security number,bank account number, salary, etc.

USER DEVICE: Any type of mobile processing device such as a handheldcomputer (e.g., phone, smartphone, tablet, personal digital assistant),wearable computer (e.g., smart watch, smart glasses), portable computers(e.g., laptop, netbooks, Chromebook), or wearable or implantable device,and the like using wireless communication, a camera or otherconnectivity element.

USER/DEVICE ID RECORD: A record stored within a database on a serverthat contains the unique ID and unique identifying informationassociated with that unique ID for each user that accesses the system.The user/device record can contain an unlimited amount of informationabout the user device and presumably the user who owns the user devicesuch as, but not limited to a history of events attended, digital offersused, gambling wagers made, NFTs minted or purchased, venues orlocations visited, concession or merchandise purchases, donations made,incident reports, tags scanned, other actions taken, etc. This mayfurther include certain information related to demographics, eventattendance history, purchasing history) as well as information about theuser device (type of device, GPS location of the device when is scans anMRC).

VENUE: Any physical location with defined perimeters and parameters suchas a stadium, arena, court, track, concert hall, theatre, course,museum, restaurant, place of worship (church, synagogue, temple, mosque,etc.), historical site, cultural site, amusement park, zoo, aquarium,conference center or any other place where events are held or usersgather. Venues can also be hotel rooms, cruise ships, trains, airplanes,schools (elementary, middle or high school) or a college campus or dorm.

WEB APP: Executable code that is stored on a remote server and deliveredvia the system or a network to a browser interface on a user device. TheWeb app may facilitate communication between the user device and one ormore servers such as the redirect/identification server or the interfaceserver.

The embodiments herein are directed toward a system and methods forprovide unique content based upon meeting a particular threshold forrelease of the content. This and other elements can be performed on thesystem as detailed in the following embodiments. A high-level overviewof an exemplary system (10) is shown in FIG. 1. The system (10) mayinclude an administrator device (12), a platform (20), a user device (14a) associated with an event user (e.g., physically at the event/in thevenue), a user device (14 b) associated with a remote user (e.g., notnecessarily at the event/in the venue), a plurality of tags (16 a, 16 b)and one or more networks (18). Generally, each user device (14 a, 14 b)may be used to scan, read, or otherwise detect (collectively “scan”)machine-readable code (“MRC”) (17 a, 17 b) associated with a respectivetag (16 a, 16 b). The act of scanning a tag (16 a, 16 b)/MRC (17 a, 17b) initiates communications between the user device (14 a, 14 b) thatscanned the tag (16 a, 16 b) and the platform (20), which may result inthe rendering of a Web page or the like (e.g., related to the event) bya Web browser and/or other application running on the user device (14 a,14 b). Communications between user devices (14 a, 14 b) and platform(20) is typically via one or more networks (18), which may include,without limitation, the Internet, mobile networks, cloud-basedplatforms, or combinations thereof.

A proprietor may use a network of encoded tags (16 a, 16 b) to identifypoints of interest (e.g., locations, objects, people, etc.). The numberof tags (16 a, 16 b) in the network and placement of tags on, in, ornear points of interest is at the discretion of the proprietor to fitits particular assets and needs. Further, a proprietor may add to orsubtract from the number of tags (16 a, 16 b) in the network at will.Thus, the number of tags (16 a, 16 b) in a proprietor's network may bedynamic, either more or less than an original network of tags. Each tag(16 a, 16 b) in the network of tags has a unique identifier (tag ID),which may be used to identify a particular point of interest. Forexample, a tag (16 a, 16 b) may be situated on or near a seat in astadium, and the user who purchased a ticket to sit in that seat is the“limited owner” or renter of that seat for a particular event. Incertain embodiments, it may be possible to have multiple copies of thesame tag, each with the same tag ID, in locations where multiple scanswould be desirable at the same time by multiple users. Thus, at theentrance to a stadium, a plurality of tags could be located at differententrance points, each having the same tag ID.

As is implied in FIG. 1, a certain number of tags (16 a) may be presentat the venue (“in-venue tag”), and additional one or more tags (16 b)may be remote from the venue (“remote tag”) where the MRC (17 b) isdisplayed in/on a video transmission, signal, or the like, or on a Webpage associated with the event, venue, and/or television network, as afew non-limiting examples. Of course, there is the possibility that auser at the event/in the venue scans the remote tag (16 b) with his/heruser device (14 a). Each user device (14 a, 14 b) may also include, ormay eventually include, a unique identifier (22 a, 22 b) to uniquelyidentify the user device (14 a, 14 b) and a digital wallet (24 a, 24 b)to securely store sensitive information such as a driver's licenses,account information (e.g., banks, crypto currencies, credit cards),titles, tokens, tickets, vouchers, coupons, other digital file (301 a,301 b), and the like.

The proprietor may also access platform (20), albeit via theadministrator device (12) and one or more networks (18). Theadministrative device may be located at the venue, or it may be at alocation remote from the venue. Generally, the proprietor may access aproprietor portal (FIG. 3 at [322]) hosted by platform (20) to performadministrative and/or other activities such as determining what content(or other) will be sent to the user device (14 a, 14 b) in response toscanning a tag (16 a, 16 b).

In addition to hosting the proprietor portal, platform (20) may host avariety of other services including, without limitation, event user andremote user access to content associated with the event, venue,proprietor, and the like. As such, platform (20) may include, or mayinclude access to, one or more servers, databases, applicationprogramming interfaces (APIs), artificial intelligence/machine learningalgorithms, other algorithms, code, blockchains, blockchain platforms,geofences, third-party integrations, times stamp, and more, which isdetailed below, with reference to accompanying figures.

FIG. 2 shows an exemplary venue (202), which includes a portion ofsystem (10) shown in FIG. 1. In this case, the venue (202) is a footballstadium including a jumbo screen (204), recording devices (206 a, 206 b,206 c, 206 d), seats (208), and a plurality of tags such as tag (16 a).Although a stadium is shown, the venue (202) can be any venue: small,large, indoor, outdoor, permanent, temporary, one structure, severalstructures, an entire city, and variations thereof. Thus, a venue (202)can be any area or space occupied by or intended for something, and assuch associated amenities and accoutrements may drastically vary fromvenue to venue. In this example, the stadium has jumbo screen (204),which may display a wide variety of video content as is customary for afootball game, though such display screen is not necessary forfunctionality of the system. The stadium also includes optionalrecording devices (206 a, 206 b, 206 c, 206 d) such as video cameras forrecording the football game and other activity, which is also customaryfor this type of venue (202). Likewise, an event may be any eventincluding sporting events, artistic performances, trade shows,conferences, ceremonies, services, self-guided tours (e.g., at museums,historic sites), and zoos as a few non-limiting examples. Notably,museums, historic sites, zoos, and similar examples may be both thevenue and the event or house the event.

In the example of FIG. 2, each seat (208) has a seatback (210) with atag (e.g., 16 a) disposed thereon. In this way, event users can easilysee a tag (e.g., 16 a) directly in front of them while they are sittingin their seats (208). Thus, the tag (e.g., 16 a) that the event usersees is associated with the seat (208) in which the user is sitting. Tagassociation with a particular seat (208) is desirable in embodimentsthat take advantage of knowing the event user's seat location such asfor food or merchandise delivery directly to the seat (208), asnon-limiting examples. In-venue tags (e.g., 16 a), however, are notlimited to being positioned on seatbacks (210); they may be placed in awide variety of locations within a venue (202). For example, if in-venuetags (16 a) are associated with particular seats (208), they may beplaced in any other location on or near the associated seat (208) suchas an arm rest, a cup holder, on the seat (208) next to the event user'sleg, on the ground, or on a structure near the seat (208) such as awall, a pillar, or the like. It should be noted that in-venue tags (16a) may be associated with other locations/points of interest, and thusmay be placed at or near the locations/points of interest such asentrances, levels, sections, isles, loge seats, individual people (e.g.,with a tagged badge, tagged ticket, or the like), restrooms, variousadditional possibilities, or combinations thereof. Therefore, while oneexample of in-venue tag (16 a) placement is illustrated in FIG. 2,in-venue tag (16 a) placement should be broadly construed to include anyplacement suitable for use as described herein. Tags (16 a) may beassociated with one or more groupings, for example, by a section, (222,224, or 226), wherein grouping of tags (16 a) may provide certainbenefits in the various embodiments detailed herein. Alternativeplacement schemes that may be devised by one skilled in the art,consistent with the teachings of the present invention, should beconsidered within the scope of the present disclosure.

As compared to an in-venue tag, in certain embodiments, it may besuitable to include one or more mobile tags. A mobile tag may be locatedwithin a movable device, for example a vehicle, a bike, a boat, train,airplane, etc. A tag on such movable devices will need to capture theGPS from the user device at the moment of capture to identify alocation. A movable tag can be accessed several times in a series oftime (e.g., minutes or seconds) and generate a different GPS locationeach time a user device scans the tag (or queries a server) and allowsthe system to identify the movement of the user device.

As was mentioned with respect to FIG. 1, each tag (16 a, 16 b) in thesystem (10) has a machine-readable code (17 a, 17 b) associatedtherewith. The term machine-readable code (“MRC”) as used herein shouldbe broadly construed to include “graphics” type codes such as quickresponse (QR) codes, universal product code (UPC), snapcodes, and/or anyother type of machine-readable graphics (e.g., having a pattern, matrix,or the like) coding known in the art or later developed. Importantly, asused herein, the term machine-readable code/MRC should also be construedto include “chip” technologies that store data on a chip such as,without limitation, near-field communication (NFC) and radio-frequencyidentification (RFID) technologies, as is known in the art or is laterdeveloped. Thus, MRC can be read, scanned, detected or otherwise decoded(collectively, “scanned”) by an appropriately enabled (e.g., camera, QRscanner, and/or NFC reader [212]) user device (14 a, 14 b).

In-venue tags (16 a) may be physical (e.g., tangible), digital (e.g.,virtual/intangible), or combinations of both forms. Physical tags may beconstructed from diverse types of materials. In the case of tags havingone or more graphical/matrix type codes such as QR codes, barcodes, andthe like, the code may be printed, etched, fabricated, or the like onmaterials such as paper, glass, plastic, metal, fabric, and the like, asa few nonlimiting examples. In the case of NFC/RFID enabled tags,chips/antennae may be adhered to, attached to, embedded in, orfabricated on (or combinations thereof) a natural or manufacturedmaterial such as metal (e.g., aluminum, stainless steel), semiconductor,wood, polymer (e.g., plastic), film, glass, and combinations thereof,without limitation. The material may be incorporated into or affixed(e.g., adhesive, or other form of attachment) where desired. Digitaltags may be displayed on a screen or communicated via radio waves. Inthe case of QR codes, barcodes, and the like, the graphical code may bedisplayed on a display screen such as the jumbo screen (204) or adisplay screen associated with the event user's seat (208), otherlocations/point of interest, or combinations thereof. Thus, the in-venuetag (16 a) may be a video display, such as LCD, LED, e-ink, or othervisual display and/or text accompanying the MRC (17 a). In fact, most,if not all, remote tags (16 b) will be a display screen such as on atelevision screen, computer screen, appliance screen, and the like,having the MRC (e.g., 17 b) displayed thereon, or text on the displayscreen identifying the MRC (17 b), although embodiments are not limitedthereto.

Information encoded on or in each tag in the system (10) may include anaddress to direct a request (e.g., for a Web page) from the user device(14 a, 14 b) to a server or the like on the network (18) such as aserver on platform (20). The address may be in the form of a uniformresource identifier (URI) such as a uniform resource locator (URL),according to a non-limiting embodiment. In this way, when the user scansthe tag (16 a, 16 b) with the user device (14 a, 14 b), the user device(14 a, 14 b) sends a request to the appropriate network (18) location.In the example shown in FIG. 3, when the event user uses his/her userdevice (14 a) to scan tag (16 a), the event user device (14 a) obtainsan address from the MRC (17 a) associated with the scanned tag (16 a)and sends a request via the network (18) to the address destination. Asone example, the address is a URL that causes the event user device (14a) to send a request to a redirect/identification server (302), onplatform (20), which receives the request. Similarly, when the remoteuser uses his/her user device (14 b) to scan the MRC (17 b) on a screen(304), a similar URL is obtained which causes the request from theremote user device (14 b) to be sent to the redirect/identificationserver (302), which receives the request.

In a typical embodiment, each tag (16 a, 16 b) in the plurality has aunique tag identification number (i.e., “tag ID”), which may be appendedto the URI/URL, although embodiments are not so limited. The tag ID maybe used by the platform (20) for several reasons, one of which is toidentify a point of interest/location associated with the tag (14 a, 14b) via a tag ID lookup. For example, when a request comes from the eventuser device (14 a), the platform (20) knows that the request came fromwithin the venue (202) and is associated with the seat (208) in whichthe event user is sitting. And when the request comes from the remoteuser device (14 b), the platform (20) knows that the request is inresponse to scanning a tag (e.g., 16 b/MRC 17 b) in transmission, on aWeb page, or the like, and the platform (20) knows whichtransmission/Web page is associated with the scanned tag (16 b). In anembodiment, the tag ID may be appended to the URL (or URI) such as byone or more parameters, pattern matching techniques, or other suchmechanism for encoding information in a URI, URL and/or browser request.

FIG. 3 details an exemplary infrastructure that may be used by platform(20) although infrastructures are not limited thereto. Thisinfrastructure may include the redirect/identification server (302), aninterface server (306), a database (308), an administration server(310), an analytics server (312), a blockchain, access to a blockchain,or both (314), a geofence (316) a timestamp (318), one or more thirdparty integrations (320), the proprietor portal (322), and a socketserver (324). Generally, user device (14 a, 14 b) communicates with theplatform (20) via redirect/identification server (302) as was previouslydescribed. Redirect/identification server (302), accept requests fromuser devices (14 a, 14 b), sends responses to user devices (14 a, 14 b),and performs various other methods as described herein. As onenon-limiting example, the redirect/identification server (302) mayforward information (e.g., URLs, parameters, etc.,) from user device (14a, 14 b) requests to the interface server (306). The interface server(306) manages most, if not all the tasks involved with processingrequests, such as handing off/directing tasks, functions, calls, and thelike where needed. The interface server (306) may also return requestresponses to the redirect/identification server (302). If a request camefrom a user device (14 a or 14 b), then the redirect/identificationserver (302) forwards the response to the requesting user device (14 aor 14 b). Examples of tasks, functions, calls, and the like that theinterface server (306) may hand off include, without limitation,database (308)/blockchain storage, lookups, etc., administrative andback-end tasks/functions to the administration server (310), analyticaltasks/functions to the analytics server (312), geolocationtasks/functions (316), time/timestamps (318), API calls to third-partyservers for third party integrations (320) and establishing socketconnections via socket server (324).

Referring to FIGS. 3 and 4 together and using the request from eventuser device (16 a) as an example, a method (400) may begin with theredirect/identification server (302) receiving the request (step 402)from the event user device (14 a). From there, theredirect/identification server (302) may check to see if the event userdevice (14 a) has a manifest (containing the unique ID, or just theunique ID alone) loaded thereon (step 404). If no, theredirect/identification server (302) may obtain a manifest and assign aunique ID (e.g., from database [308]) for the event user device (14 a,step 406). The manifest includes a unique ID to identify the event userdevice (14 a) with an identifier that is not shared with any other userdevice (e.g., 14 b). The redirect/identification server (302) will alsocause the unique ID for the event user device (14 a) to be stored in adatabase such, as database (308), as is appropriate for the databasemanagement system (step 406). As used herein, the term “record” refersto information that is stored in an electronic or other intangiblemedium without limitations on how the data is structured. A record mayinclude and/or point to related data. For example, a record for a uniqueID may include the unique ID and any other data related thereto, whichmay be stored in database (308) or other appropriate data storage. Afterobtaining the manifest and/or the unique ID, the redirect/identificationserver (302) may then send the manifest together with the unique ID tothe event user device (14 a, step 408), which may be maintained on theevent user device (14 a) in a digital wallet, other secure repository,or both. At step (410), the redirect/identification server (302) maymaintain a copy of the unique ID for further use in the method (400),other methods described herein, or both. If the event user device (14 a)already has a manifest (step 404, yes), the redirect/identificationserver (302) obtains the unique ID from the manifest (step 410). In anembodiment, the redirect/identification server (302) may also obtaindata such as current time, date, location, etc. from the event userdevice (14 a), manifest, request, or combinations thereof at step (410).

In an embodiment, the redirect/identification server (302) may passinformation needed to further method (400). For example, the tag ID maybe passed to the interface server (306) for a tag ID lookup (step 412),such as in database (308), the administration server (310) and/or anyother suitable database or server. In this instance, theredirect/identification server (302) obtained the tag ID from therequest made by the event user device (14 a). In an embodiment, the tagID is appended to the URL, and thus the entire URL, or a portionthereof, may be passed to the interface server (306) for use in lookingup the tag ID. Looking up the tag ID provides information about thevenue (202) and/or event. To clarify, when a particular venue (202)installs tags (16 a) and/or uses tags (16 b), the tag IDs for theinstalled/used tags (16 a, 16 b) are associated with the point/locationof interest and the particular venue (202). Thus, if a tag is installedproximate seat 1, row A, section 100, database (308) informationassociates the installed tag's (16 a) tag ID and that particular seat(208), which is in that particular venue (202). Since the tag ID isknown to belong to a particular venue (202), the interface server (306),the administration server (310) via the interface server (306), anyother suitable server, or combinations thereof makes a series ofdeterminations using the tag ID, which was received in response to arequest from a user device (14 a, 14 b) prompted by scanning the tag (16a, 16 b). One determination is if the venue (202) is activelyimplementing platform (20) services (step 414). For example, the venue(202) may have tags (16 a) installed but it is no longer using the tags(16 a), or it is not using the tags for a particular event. If not, theevent user device (14 a) is redirected to a global default target (step416) that may inform the event user that the services are no longeravailable, are temporarily out of service, or the like. If the venue(202) is actively implementing platform (20) services, the method (400)may make another determination. At step (418), the method (400) maydetermine if a particular event is currently (or soon to be) inprogress, or recently ended. In an embodiment, an event may bedetermined to be in progress based on the time that the event isscheduled to begin. Since many venues (202) open before the actual eventbegins, and close after the actual event ends, the window set for anevent to be in progress may encompass a given amount of time before andafter the actual activity begins/ends. In an embodiment, the time thatthe “event in progress” determination is made (step 418) may be recordedto serve as a timestamp to approximate the time that the event userdevice (14 a) scanned the tag (16 a). In other words, the unique ID, tagID, and time determination may be recorded for later use, in certainembodiments. If the event is not in progress, the event user device (14a) may be redirected to a venue default target (step 420) such as a Webpage for the venue, or another Web page such as a page to identify thatan incident has occurred at the venue (202) at the location/point ofinterest in which the tag (16 a) was scanned. Incidents may encompassany sort of incident such as a need for something to be cleaned up tocalling emergency services.

If the event is in progress, the method (400) may also determine if thetag ID belongs to a grouping of tag IDs (step 422). Tags (16 a, 16 b)may be grouped for many reasons and in many different ways. Tags (16 a,16 b) may also belong to more than one group. As one non-limitingexample, in the stadium of FIG. 2, the tags (16 a) may be grouped byseating type or section (e.g., FIG. 2, 222, 224, or 226), e.g., VIPseats may belong to one group, loge seats to another group, anddiscount/student seats may belong to yet another group. If dataassociated with the tag ID indicates that the tag belongs to a group,the event user device (14 a) may be redirected to a target for theparticular group. For instance, the target for users sitting in VIP orloge seats may be a Web page associated with event that includes premiumcontent, offers, and the like, whereas the target for users sitting indiscount/student seats may be a Web page having content and featuresthat typically appeal to students, recent graduates, or the like. Thus,the method (400) obtains the information it needs to enable redirectionto the appropriate group target (step 426). If data associated with thetag ID indicates that the tag does not belong to a specific group, theevent user device (14 a) may be redirected to an event default targetsuch as a standard Web page for the event. Thus, the method (400)obtains the information it needs to enable the redirection (step 424) tothe default target for the event. In an embodiment, the informationneeded for redirection may include a URL for the target with parameters,values, patterns, or the like appended thereto such as a target ID toidentify the target and the tag ID.

Method (400) may simultaneously process other data such as looking upone or more records associated with the unique ID (step 428). Inembodiments, the platform (20) may gather information relating to useractivities via the user device and unique ID. For example, the platform(20) may gather data relating to tags that the user has scanned in thepast (across a variety of different events, venues, or the like) andactivities associated with those tag scans (e.g., purchases made,content looked at, coupons downloaded), although embodiments are notlimited thereto. This data may be stored in association with the uniqueID assigned to the event user device (14 a). Thereafter, a controllermay associate the unique ID, its record, its record location or the likewith the tag ID, target ID, a URL, any other determined information, orcombinations thereof (step 430). The event user device (14 a) may thenbe redirected to the appropriate target that has been determined for theevent user device (14 a).

When a request comes from a remote user device (14 b), the method (400)starts out essentially the same as with the event user device (14 a).That is, the redirect/identification server (302) receives the request(step 402), checks for a manifest containing a unique ID (step 404),assigns a manifest with a unique ID if one has not yet been assigned(step 406), and sends it to the remote user device (14 b, step 408) forsecure storage thereon. If the remote user device (14 b) has a manifest,then the redirect/identification server (302) obtains it (and otherinformation such as a unique ID) from the remote user device (14 b).Either way, the redirect/identification server (302) has the informationthat it needs such as unique ID, URL, tag ID, and the like, and forwardsthe information to the interface server (306) to continue the method(400). The interface server (306) may then look up, or cause to look up,the record associated with the unique ID (step 428) assigned to theremote user device (14 b). At the same time, the interface server (306)may cause a determination to be as to whether the venue exists (step414). In this case the interface server (306), or other server, may lookat the data associated with the tag ID to determine from where the tag(16 b) that was scanned originated. For example, the MRC (17 b) may haveoriginated from a particular signal, transmission, etc., (e.g., network,regional network, etc.), Web site (e.g., for the venue, a streamingservice, etc.) or the like. If, the method (400) determines that thevenue does not exist, for example, if the tag is to an unrelatedelement, then the remote user device (14 b) is redirected to thatunrelated element or to a global default target (step 416), for exampleif the tag is related. Assuming that the venue in this case does exist,the interface server (306)/method (400), then determines whether theevent is in progress (step 418). If the signal, transmission, Web page,or the like is transmitting an event as it is occurring in real timethen the event is in progress. Such can also be determined by a timestamp or time record set within the system. Either way, in anembodiment, the time the determination is made may be recorded by theplatform (20). If the event is not occurring in real time (e.g., theuser is watching a recording after the fact), then the remote userdevice (14 b) will be redirected to an appropriate target such as a Webpage relating to the event (step 420). However, the proprietor can setany time parameter to define “real time”. For example, a proprietor maydesire to allow recordings watched within N number of days of a liveevent to constitute real time. The interface server (306) may thendetermine if the tag (16 b), via the tag ID belongs to a group (step422). For instance, different tags (16 b) may be associated withdifferent signals, transmissions, Web sites, or the like. Some of thesetags (16 b) may form groups based on predetermined criteria. Thus, ifthe tag (16 b) belongs to a group, the remote user device (14 a) will beredirected to the target for the appropriate group, and if not, theremote user device (14 a) will be redirected to the default target. Thedefault target for remote users may or may not be the same default forevent users. Either way, the information relating to the determinedredirection target is obtained (steps 424, 426). At step (430), acontroller may associate the unique ID, the record for the unique ID, apointer to the record for the unique ID, the tag ID, and targetinformation such as a URL, target ID, or both. Thereafter, the remoteuser device (14 b) is redirected to the appropriate target (step 432),as was described with respect to the event user. In certain embodiments,the step of (428) may be provided in parallel to or concurrent with thelookup of the tag ID (step 412), where the unique ID is necessary fordetermining any of the other elements. Furthermore, the unique ID may bestored, for example in local memory or cache, which is readilyaccessible or known to the system after step (410).

In an embodiment, the user device (14 a, 14 b) may receive a redirectURL from the redirect/identification server (302) at the end of method(400) to redirect the user device (14 a, 14 b) to the appropriatetarget. For instance, the method (400) may return a target ID toidentify the particular target. The target ID, tag ID, unique ID (and/orinformation associated therewith), or combinations thereof may beappended to the redirect URL for the target, which is sent to therequesting user device (14 a, 14 b). The requesting user device (14 a,14 b) then uses the redirect URL to send a new request, this time forthe target, which is received by the redirect/identification server(302) and is forwarded to the interface server (306) for processing.Alternatively, the target ID, tag ID, and unique ID may be used by theplatform (20) without sending a redirect URL to the requesting device atthe end of method (400). Regardless of the forgoing, the requesting userdevice (14 a and/or 14 b) receives the target of the redirectionwhatever that target may be. For example, a target may be a static Webpage, a dynamic Web page, an application delivered by way of one or moreWeb pages, files, data, information, or combinations thereof. As onenon-limiting example, the fan portal (218) may have been the targetidentified by the target ID, and it may include application code“wrapped” or embedded in in an HTML document. Application code includes,but is not limited to, Web application code, progressive Web applicationcode, cloud-based application code, native application code, nativemobile application code, other such code, or combinations thereof. TheHTML document (and cascading style sheet, etc.) generally determines theformat/layout of what the user sees as is known in the art.

Furthermore, targets are not necessarily static. In fact, the same tag(e.g., 16 a) may cause a user device (e.g., 14 a) to be redirected todistinct targets depending upon when the particular tag (16 a) isscanned. For example, a venue (202) hosts many events over the course ofa season, year, decade, etc. Each event may have its own target as theindividual events are distinct. For example, the fan portal (218) may bethe target of a game in progress, such as the football game shown inFIG. 2. The game in progress is between team A and team B. The next game(or other event) hosted at the venue (202) may be a soccer game; thus,the fan portal (218) for the soccer game is different from the fanportal (218) for the football game. In other words, the two fan portals(218) are distinct targets for redirection. The target that is reachedby scanning the tag (16 a) is coordinated with targets, such as via adistinct target ID, so that the user device (14 a) is redirected to thefootball fan portal (218) during the football game and the same userdevice (14 a) can be redirected to the soccer fan portal (218) duringthe soccer game even though the exact same tag (16 a) is scanned by theexact same user device (14 a). Of course, this is one non-limitingexample. A single tag (16 a) may be used by a proprietor to redirect auser device (14 a, 14 b) to any desired target. Thus, the target towhich the user device (14 a) is redirected may be changed fromgame-to-game.

A proprietor may also change a target during the course of a particularevent. For example, referring again to the fan portal (218) shown inFIG. 2, the user may use the fan portal (218) to partake in activitiessuch as buying food or merchandise, placing a wager, view replays (220),the delivery of a target based on a trigger, etc.

One unique aspect is related to dynamic content. At any time during theevent, the jumbo screen (204) may display a hidden “unique offer” (214)that is only available to the first 1,000 users who respond to the“unique offer” (214) after it is displayed on the jumbo screen (204) byscanning a tag (16 a) or the like. A countdown (216) on the jumbo screen(204) shows the number of event user devices (14 a) that have claimedthe “unique offer” (214). When the threshold number (1,000) is reached,the unique offer may be revealed and is no longer available to any otherusers. This countdown and the limited nature then become a type ofdynamic content. One way an event user may respond to the hidden “uniqueoffer” (214) is by scanning or rescanning the tag (16 a) while theunique offer (214) is available. In this case, the user device (14 a)may be redirected to a Web page or the like, for the unique offer (214),e.g., to input information, make payment, or the like, per a processthat is the same as/similar to the method (400). The redirect target ofthis scan, however, is the “unique offer” (214) and not the fan portal(218). Another way a user may be able to respond to the “unique offer”(214) is by a pop-up window (e.g., in/over the fan portal [218]) or thelike, which may be pushed via the socket server (324) in a non-limitingembodiment. Thus, the term “target” should be broadly construed althoughit may be described herein with respect to obtaining a fan portal (218)or other specific examples. One of ordinary skill in the art wouldunderstand a target of redirection as described herein may be amultitude of different targets with various purposes, designs,capabilities, and the like. Therefore, the target to which a particulartag (16 a, 16 b) is assigned, may be changed by simply changing thetarget identifier (“target ID”) associated therewith.

There may be instances where the content delivered via the target mayneed to be changed, updated, altered, released, opened, or other suchstipulations based on a rule and/or other conditions. Rules may bedefined to force a modification of content already delivered, deliveradditional content, information, data, release content, and/or makeother such changes as would be appreciated by one skilled in the art. Inthis non-limiting example, the target delivered at (432) FIG. 4 includesa Web application, such as a progressive Web application (PWA), that hasa pull function, which may be rule-based. The pull function, as onenon-limiting example, may be time based, requesting information to bepulled from the platform (20) via the interface server (306) every 10seconds, minutes, N seconds, N minutes or the like. As anothernon-limiting example, the pull function has the ability to have dataupdated on a rolling basis. In the sporting world, this is common whenupdates are provided to the score of a game, the time left in a game, orboth as non-limiting examples. The platform (20), however, may pushrolling data to a user device (14 a, 14 b) instead of having it pulledfrom the platform. Pushed data may be sent to user devices (e.g., 14 a,14 b) without being requested. Data may be pushed to a user device (14a, 14 b) for any number of reasons, a few of which are detailed herein.Thus, information, data, etc., may be pushed to a user device (14 a, 14b), pulled for a user device (14 a, 14 b,) or both. In many instances, aWeb application or the like may be based on a template having dynamicelements embedded therein. The contents of such dynamic elements may bealtered via push techniques, pull techniques, or both. Content, data,information, and the like, may be pushed and/or pulled via a socketconnect utilizing a socket server (324) or any other socket connection,communication connection, protocol, or combinations thereof as isavailable to the platform (20) under a set of given circumstances.

The method detailed in FIG. 5 may be invoked while the target ofredirection (e.g., fan portal [218]) is loading on the requesting userdevice (e.g., 14 a and/or 14 b), after the target is already loaded onthe requesting user device (14 a and/or 14 b), or both. As with allmethods detailed herein, steps in the method (500) may be used in wholeor in part, in the order shown or a different order, be executed on onedevice or more than one device, be used in combination with some/all ofthe other methods described herein or as is known in the art, orcombinations thereof.

Using fan portal (218) as a non-limiting example while referring to FIG.5, oftentimes it may be desired to alter information, regardless of type(e.g., video, images, instructions, etc.,) while the user is using thefan portal (218). Information may be altered using push, pull, and othertechniques, taking advantage of the communication connection (504). Thecommunication connection (504), which may be a socket connection or anyother appropriate type of connection, allows communications between theuser device (14 a and/or 14 b) and the platform (20) via the one or morenetworks (18). A controller (at 506) may be a set of software code formanaging, directing, or generally being in charge of one or more rules,enabling pushing and/or pulling of information per the rules. In thisexample, rules may be used to change content on the user device (14 aand/or 14 b). The interface server at (510) may be the same interfaceserver shown in FIG. 3 (306), just at the data sources at (512) may bethe same data sources shown in FIG. 3 such as database (308),administrator server (310), analytics server (312), blockchain (314),geofence (316), time (318), third party integrations (320), andproprietor portal (322), without limitation. Moreover, interface serverat (510) may facilitate utilization of the forgoing, in the same manneror similar manner as described with respect to FIG. 3. Thus, in a sense,user device (14 a or 14 b), communication connection (504), interfaceserver (510), and data sources (512) are shown in FIG. 5 just to helpthe reader visualize interactions detailed in FIG. 5.

Examples of rules that are detailed with respect to FIG. 5 include eventrules and local rules, although embodiments are not so limited.Generally, an event rule is monitored by the platform (20) and ifsatisfied causes data to be pushed to one or more user devices (14 a, 14b) and a local rule, when invoked, causes a user device (14 a, 14 b) torequest data (i.e., pulls data) from the platform (20). An illustrativeexample of an event rule is if team “A” scores a touchdown, push adigital offer to all user devices (14 a, 14 b) that have scanned tags(16 a, 16 b). Here, the metric or trigger of the rule can be monitored(step 516) such as by directly sending a request or query to a datasource (at 512) via the interface server (at 510), receiving data fromthe data source (at 512) on a regular basis such as every 5 seconds, 5minutes, or the like (via the interface sever [at 510]), or combinationsof both. The platform (20) may to monitor for the metric/trigger e.g., atouchdown (step 520) and continue to do so (step 522) until ametric/trigger e.g., a touchdown has occurred (step 520, yes). If therule has been satisfied, the platform (20), can push the digital offerto all of the qualifying user devices (i.e., that have scanned a tag [16a, 16 b]).

A more complex event rule may include more than one trigger/metric. Forexample, the rule may be that if team “A” scores a touchdown, push adigital offer for a free beer to all event users over the age of 21 thathave used their user device (14 a) to scan a tag (16 a) in the venue(202). The first metric/trigger of whether a touchdown has been scoredmay be monitored as described above. The second metric/trigger may bemonitored (at 518, 524) in the same or similar manner if themetric/trigger warrants, or it may be determined before or after thefirst trigger/metric has been satisfied. For example, since in thisexample the second metric/trigger relates to age, a query may be sent toone or more data sources (at 512) to find all users who are over the ageof 21. Records stored on database (308), for example, may be consultedto look for age data in connection with unique ID data to determine ifthe person who has loaded the fan portal (218) on his/her device (14 a)is of legal drinking age. As an alternative source of data or for anyother reason, the interface server (at 510) may cause another datasource (at 512) to be consulted to determine user age. For example, oneor more third party integrations (320) may have age information; thus,an API call or other query may be made to the third party integrations(320) to obtain age data. As with the first example, if the firstmetric/trigger (step 520, no) is not met (i.e., touchdown), then theplatform (20) continues to monitor the metric/trigger (step 522). If themetric/trigger (step 520, yes) has been met the platform (20) determinesif the second metric/trigger (518) has also been met (step 524). Wherethe second trigger/metric has not been met (step 524, no) then thetarget on the user device (14 a) is not updated (step 528), such as withthe digital offer. Depending upon the rule, the second metric/triggermay continue to be monitored or not. For example, if the digital offerwas to be sent only one time, then the rule is satisfied, and noadditional monitoring is needed. If, however, the rule is to send thesame digital offer (e.g., for a beer) every time team “A” scores atouchdown, the second metric/trigger would not have to be redeterminedsince even if the user turned 21 that day, the user's age would notchange. Of course, if the event went past midnight, the rule could bestructured to recheck ages after midnight. This does not mean that for agiven rule a second (or third, or fourth, etc.,) trigger/metric wouldnever need to be monitored. Should an additional metric/trigger bedefined by a rule that needs additional monitoring, the method (500)will be allowed to do so. Going back to step (524), if the determinationis yes, the digital offer may be pushed (526), such as via thecontroller (at 514, 506) to those users who have scanned a tag (16 a)and who are at least 21 years old. Pushed content may update an element,such as a dynamic element, on a Web page, cause a popup to show on theuser device (14 a, 14 b), send content to a digital wallet (24 a, 24 b),or any other way to push content as is known in the art.

Local rules, as an example, may be associated with one or more targetsbeing utilized for a given event. Referring again to FIG. 2 as oneexample, each section of seats (222, 224, 226) may represent a groupingof tags (16 a) such as student/discount seats, loge seats and all otherseats. As such, when a tag (16 a) is scanned by a user in section (222)the device (14 a) may be redirected to first template of fan portal(218), when a tag (16 a) is scanned by a user in section (224), the userdevice (14 a) may be redirected to a second template of a fan portal(218), and when a tag (16 a) in section (226) is scanned the user device(14 a) it may be redirected to a third template for a fan portal (218).Thus, all users may be redirected to a fan portal (218), but each fanportal (218) may be based on a different template. In this way, aproprietor may deliver customized content to users in different sectionsbased on the template to which the user device (14 a) was redirected.Local rules, other elements, or both may be written into each templateto further customize content, which in some instances may be on anindividualized level. That is elements of application code may be rulesbuilt into the system to provide the content delivery determined by thesystem, or can be applied at an earlier stage, e.g., at a tag ID grouptarget information (step 422), which can provide a different originalredirect URL/target than is received by or directed to, for another tagID in a different group.

Referring back to FIG. 5, the interface server (306, at 510) maydetermine, or cause to be determined, if there are any rules associatedwith a given template (e.g. for fan portal [218]) or another target.This is especially true where the rule may be designed as an event-typerule where content may be pushed to a device (14 a). In this case,however, the rule may only be provided in a given template (e.g., forusers sitting in loge seats). A given template, however, may also havelocal rules written therein. For example, a rule associated with a fanportal (218) template to be distributed to loge seats, may be if theuser has season tickets, then include a digital offer for discountedseason tickets for the following year. Thus, per this illustration thelocal rule may desire to pull/acquire (at 508) season ticket informationbefore, during, or after the template for the loge seats is loaded onthe event user device (14 a). To obtain this data, the database may bequeried (at 512), via the interface server (at 510), using the unique IDto check data records for the requested information (e.g., purchasedseason tickets). As with the push example, if the database (at 512) doesnot store such information, the information is inconclusive, the localrule requires confirmation from an outside source, or other suchsituations, other data sources (at 512) may be consulted via theinterface server (at 510). If the local rule is satisfied, then adigital offer for discount tickets (next season) is sent to thetemplate. If the local rule is not satisfied, then the template uses a“default” digital offer/content such as an ad for non-discounted seasontickets, upgraded tickets for the next event to be held at the venue(202) or another, similar example. In an embodiment, data associatedwith the unique ID may be pre-analyzed to see if the local rule has beensatisfied. Alternatively, data associated with the unique ID may begathered (e.g., from a database, a third-party integration such as aticketing service, or the like) and analyzed when the event user device(14 a) makes the request. As yet another option, the data may bepre-analyzed and verified/checked for changes upon the event user device(14 a) request. The interface sever (306) may take all of the variablesfrom the target application code, template, rules, and the like and sendrequests/queries to the appropriate data sources or links to the datasources (at 512). The data sources may include data from the database(308), blockchain (314), geofence (316), timestamp (318), third partyintegrations (320) such as data servers/databases, analytics server(312), and administration server (310), and a counter (at 512), withoutlimitation.

In some implementations, a counter may be needed. For example, a countermay be enabled to maintain the countdown shown in FIG. 2 (216). Acounter may be software on platform (20) that may be used as a countingmechanism for rules or other reasons. As such, the counting mechanismmay be configured to meet the counting requirements of a rule or othercounting need. As an illustration, a counter may count the number oftags (16 a) scanned in a venue (202) during a particular event; countthe number of tags (16 a, 16 b) scanned by a particular user device (14a, 14 b) in a predetermined time window; count the tags (16 a) scannedby a particular user during a particular event; count the number oftimes a user has interacted with the target delivered to that userdevice; or other such non-limiting illustrations.

Thus, while a target is displayed on a particular device (14 a, 14 b),dynamic content may be seamlessly and dynamically updated/changed percoding/interactions between the user device (14 a, 14 b) and theplatform (20). Certain dynamic changes occur through push and pulltechniques such as those detailed by FIG. 5. However, dynamicupdates/changes may further take place through the use of variousthird-party application programming interfaces (APIs) and theirrespective functionality. At a high level, the interface server (306)may connect, or may cause the third party integration server (320) toconnect, to third-party hardware/software (e.g., server) via one or morethird-party APIs/API calls to access the respective third-partyintegration/functionality as is known or will be known in the art. Thus,third-party integrations/functionality may push or pull informationthrough analytics server (312), retrieve it from database (308) oranother data store, or combinations thereof, for real time/livestreaming, updating, changing, and the like as is called for byrules/instructions associated with the target of the tag ID.Furthermore, embodiments allow for the use of interactive, two-waycommunications between user devices (14 a, 14 b) and the platform (20)such as via the socket server (324) and/or a socket API, or the like asis known in the art. Certain communications then end, upon the end ofthe event or where the user closes the application, where thecommunication (at 504) is severed.

As is also indicated in FIG. 5 at (508), the platform (20) may collect alarge amount of data via user devices (14 a, 14 b). For example, afterscanning a tag (16 a, 16 b) the platform (20) may receive data from theuser device (14 a, 14 b) such as date, time, and GPS or other location,the device orientation (i.e., landscape, portrait), type (e.g., iPhone,Android), IP and other addresses, and operating system as a fewexamples. Thus, methods such as methods (400, 500, or both) may beconfigured to collect and aggregate data. Additionally, tools such ascookies, widgets, plug-ins, and similar tools may also be used to obtaindata from user devices (14 a, 14 b). This, and other, information may bestored in a data source (at 512) such as database (308) or other datastorage and in association with the unique ID. Data acquired using theaforementioned tools and other tools/techniques may relate to userengagement with a target such as a fan portal (218) as one non-limitingexample. Such data may relate to digital offers presented to the user,digital offers downloaded by the user, products viewed by the user,purchases made by the user, to name a few examples. Suchtools/techniques may also gather data relating to other user engagementssuch as total screen time, Internet browsing (times, sites/pagesaccessed, software used), updates to Web pages, other Web sites visited,the Internet, and the like. The user may also directly provideinformation via the user device (14 a, 14 b) such as by inputtingpersonally identifiable information to obtain opportunities or offerssuch as unique information relating to user interests, user responses toquestions, generic information about age or sex, or any other type ofpersonally identifiable information. Such data is of high value to, forexample, advertisers, proprietors, and the like, as it provides a largeinsight into consumer purchasing and Web browsing habits.

Data related to user devices (14 a, 14 b) may also be obtained fromthird party sources. As one example, when a query, request, or the likesent to a third party, the platform (20) may provide certain informationwith that query, request, etc., such as the unique ID, tag ID/targetinformation, or combinations thereof. Thus, data returned by the thirdparties may also be stored (e.g., temporarily, or persistently) inassociation with unique IDs, tag IDs, target information, orcombinations thereof. As one non-limiting example, service providerssuch as mobile/cellular providers may be queried to obtain informationabout user devices (14 a, 14 b). The unique ID identifying a particularuser device may be sent to the service provider to obtain informationabout the particular device, or the service provider may provideinformation that may be later associated with a particular device.Either way, the platform (20) may collect and store information aboutusers via the unique ID assigned to each user device (14 a, 14 b). Asanother non-limiting example, information associated with unique IDsassigned to user devices (14 a, 14 b) may be collected from variousthird party integrations (320) such as in-venue/event metrics,integrated third-party metrics, ticket brokerage, and other tools,without limitation to the forgoing. In-venue/event metrics may includedata collected relating to the venue, event, or both. For example,information relating to user purchases at the venue and/or during anevent such as tickets, food, merchandise, and upgrades and the like mayall be gathered and stored in association with the unique ID. Similarly,ticket brokerage integrations (e.g., 320) may be used to gatherinformation from ticket brokers who sell tickets for the venue (202),event, or both, and may include a wide range of marketing data, not onlyabout ticket purchases made, but also related information about theuser. Thus, third-parties, including third party metrics integrations(320) may enable collecting information about users, user devices (14 a,14 b), or both from third-parties including those who participate in ashared program or who sell or otherwise provide marketing information,demographics, and other data about the user.

In addition to collecting and storing data associated with unique ID,the platform (20) may analyze such data, which may or may not berecorded in association with unique IDs. Data analysis may occur whileit is being collected, after it is collected and before it is stored,after storage, or combinations of the forgoing. Data, raw, analyzed, orboth, may be stored in database (308) or another data store (at 512)such as blockchain (314), without limitation. The analytics server (312)may communicate with various aspects of the platform (20), to ensuredata received from various sources is appropriately captured fordecision making, analytics, and the like. That is, analytics server(312) may communicate with (either directly or via the interface server[306]), user devices (14 a, 14 b), third parties, third partyintegrations (320), time/timestamp (318), geofence (316), blockchain(314), database (308), even proprietor portal (322), or combinationsthereof, so that data is captured as needed for desired analytics,decision making, and the like. For example, data may be subject toartificial intelligence analysis include machine learning/patternrecognition/deep learning as is now known or will be known in the art.Collected and/or analyzed data may be coupled with other informationrelating to the user/user device (14 a, 14 b), such as the unique IDassociated with the user device (14 a, 14 b) for a variety of reasons,including content selection as one non-limiting example.

Content for display on user devices (14 a, 14 b) may be customized innumerous ways as has been detailed with respect to methods (400 and/or500). Content may also be customized where data/data analysis shows thata user has, or group of users have particular preferences. Thesepreferences may be utilized to modify content, such as advertisementsthat are delivered to that user/group of users. Furthermore, dataanalysis may allow the proprietor to generate rules specific to auser/group of users, send custom e-mails, push socket notifications orother messaging based upon the user's interactions/group of users'interactions with the platform (20), other such similar examples, orcombinations thereof. Indeed, this provides for multiple opportunitiesfor interaction and communication between the proprietor and the user tocontinue building relationships that can then be mined for longer-termrelationships. As yet another implementation, the platform (20) mayutilize unique IDs together with known information associated therewithto deliver unique advertising to users via third-party advertisingservices. For example, where available, the platform (20) has theability to interface with advertising platforms to deliver a customizedexperience based on the user's search history or user information as awhole. Taking the forgoing together, it should be apparent that contentprovided to a particular user or group of users may be customized ormodified as was described above with respect to FIGS. 4 and/or 5 andthat data/information gathered as the user is engaged with the eventtarget or the like, may be used to update/modify target content in realtime, upon a subsequent scan of tag (16 a, 16 b) by the user device (14a, 14 b), or both (e.g., at 508). For example, the socket connection (at504) may be used to deliver pulled content, push content, notifications,and the like, and/or dynamically update content while the event is inprogress. Indeed, such socket connection may be particularly usefulwhere a plurality of users are online at one moment and the totalcreates an occurrence of a trigger which provides some dynamic contentto be released, for example, through a push of that target to the thenactive user devices that have met the limitation to receive that target.

Analytics may also determine which feature, elements, or the likeprovided by a target such as the fan portal (218) a user or group ofusers interact with the most or spend the most time viewing. Thus,advertising on high-usage pages, features, elements, etc. may come at ahigher cost. In other words, proprietors may charge a premium toadvertisers wishing to purchase the ability to place content, such asadvertisements or digital offers on the pages or features of the fanportal (218) or other target that receive the most traffic.

The forgoing has been described largely with reference to a sportsenvironment where event users can scan tags (16 a) located proximateeach seat (208)/other point of interest or remote users can scan MRCs(17 b) that appear on a screen such as a television or computer display.Other environments may utilize the same sort of tag (16 a) placementstrategy, such as an artistic performance where tags (16 a) may beplaced proximate a seat. However, many artistic performances are nottelevised or otherwise visually distributed while the performance istaking place. Thus, these proprietors may enable an option for patronsat a specific donation level, or season ticket holders to remotelyaccess the performance as the performance is taking place such as via anaccount on a Web site where the user can scan an MRC (17 b).Alternatively, certain remote users may receive a digital communicationsuch as an e-mail or physical communication such as a card or badge thatis similar to a credit card having information encoded thereon so thatthe remote user can scan the MRC (17 b) on the badge to access thetarget that is associated with the scanned MRC (17 b). In this way,remote users that are unable to attend a particular live performance maystill be able to enjoy the performance or features thereof via platform(20). And since the target for remote users may have distinctivefeatures enabled (e.g., replays, filters) during a performance that arenot available to an event user (so as to not distract the performers)the remote user may be able to watch the entire performance on theremote user device (14 b) and access other target features during thelive performance.

Concerts and concert/festivals (collectively “concerts”) may utilize thetags (16 a) already in place at the venue (202) in which the concert isbeing held if the proprietor so allows; alternatively, concertproprietors may utilize a system that is not attached to the venue(202), or they may use both. As an example, concert proprietors mayinclude tags (16 a) separate from or integral with concert tickets,passes, credentials, or the like so users can scan (or click on ifdigital) the MRC (17 a) to access the desired target. In an embodiment,the ticket, pass, credentials, or the like may be a badge or badge-likeso that it can be attached to a lanyard, put in a wallet, etc. Lanyardsmay be distributed with the ticket, pass, credentials, etc., or they maybe purchased. As an incentive to purchase a lanyard, the lanyard may beassociated with its own tag (16 a) and associated target (e.g., adigital offer). In an embodiment, remote users who are unable toactually attend the concert may still be able to enjoy certain aspectsof the concert via the tag (16 b) associated with a ticket, pass,credentials, etc. In an embodiment, remote users may opt to purchasejust a tag (16 b) so that they may enjoy certain aspects of the concertwithout being there. As one non-limiting example, the tag (16 b) mayenable the remote user to access live or recorded video of the concert,which would not otherwise be available without concert attendance.

In the case of schools and the like, tags (16 b) may be linked toparticular students and distributed to students and parents alike. Forexample, the student's tag (16 b)/MRC (17 b) may be on the student'sschool-issued ID or student-related identifier, and the parent's tag (16b)/MRC (17 b), which may be the same as or different from the student'sMRC (17 b), may be distributed to parents on a magnet, badge, card, orthe like so that the student/parent can simply scan their respectivetag/MRC (17 b) (with respective user device [14 b]) to access a target(e.g., a Web page) with information relating to the particular studentsuch as grades, classes, upcoming activities, as a few non-limitingexamples. In fact, with respect to graduation, concerts, sports eventsand the like, a secondary target may be accessed via a link in the“primary” target, although embodiments are not so limited. That is,parents, teachers (with their own tag/MRC (16 b/17 b) to connect to thedesired target), other employees and the like may access targets (e.g.,a Web page or the like) for events relating to the school in more thanone way. One way may be via the tag/MRC (16 b/17 b) that may be used ona regular basis as described above, or via tags (16 b) permanently ortemporarily placed at the school gym, auditorium, or the like, whichwill enable access to the event-specific target/target content.

Historic sites, museums, zoos, and the like may use any of the forgoingstrategies and other unique strategies to enhance visitor experiencesvia one or more targets of a tag (16 a, 16 b). As one non-limitingexample, tags (16 a) may be located at or near entrances for users toscan with their devices (14 a) to obtain the target. Additional tags (16a) may be located at, near, within, etc., various exhibits to providesupplementary content. In this way, the target of the tag (16 a) may bestreamlined and supplemented at-will. In an embodiment, users may buymerchandise/concessions via in-venue tags (16 a) much like the stadiumexample. By making a purchase, the user may use a tag (16 a) associatedwith the purchase to connect to yet another target for that particulartag (16 a) such as a coupon, discounted entry tickets, and free entrytickets as a few non-limiting examples. In fact, with any of theforgoing examples tags (16 a, 16 b) may be placed on or with merchandiseof all sorts to be able to access targets such as coupons and/or otherincentives.

The system (10) therefore can be implemented in entertainment venues, aswell as other areas where user engagement is desired and/or required,such as college dorm rooms, hotel rooms, cruise ships, trains, aircraft,rideshare vehicles and the like. While some examples of the uses of thissystem are discussed herein, the scope of the present invention shouldnot be limited to the specific examples provided, and the term “venue”should be construed to include alternative or equivalent embodimentswhich could be devised by one skilled in the art.

As discussed in greater detail below, a differentiator of the system isthat it uses data input from several variables in order to providereal-time content to the end user, specifically at a trigger of somepredefined requirement or rule. These data sets can be from a multitudeof sources such as ticket brokers, which can provide details on a userwho purchased tickets to an event, or to advertising database data,which can provide past content interactions from various sources on andoff the Internet for a particular user. These analytical datasets canalso be used to provide in-venue content or offers to users inside of anevent on an individual basis, on a group basis, or to the venue as awhole venue based upon the collected data/feedback gleaned from usersinside of the venue (i.e., if the analytics portal data reveals that 75%of users select hamburgers as their favorite type of food, the in-venuemultimedia displays would be triggered to display content relevant tothe selling of hamburgers). The system can also implement machinelearning algorithms which, when coupled with a combination of some orall of the data provided from the analytics (312) and database (308),can provide real-time content that is predicted to be favorable to theend user. The fan portal can be in various forms from browser-based Webpages, cloud-based Web apps, progressive Web apps, downloadable apps,etc. The system could provide multiple options to the fan portal such asordering food, purchasing merchandise to be delivered to a seatlocation, viewing replay footage, and/or placing wagers inside of thestadium. The system would provide the ability to offer all tags on thesystem the same interactive content options, or to offer differentcontent to users based on predetermined data sets or based on variablesand data within the system.

Because of the known location of the tag, whether static or movable, theprecise location, or GPS location can be utilized as part of the data togenerate content to the user device. Similarly, an API related to avehicle can identify a starting location and an ending location of thevehicle trip, to the extent that one is available. Accordingly, the APIcan provide data to the system that identifies the planned route of thevehicle and content relevant to that particular location may be providedto the user along that route, which may be attractive to the user. Datafrom the views, page views, time spent on a page, advertisements viewed,or digital offers downloaded by the user can provide further dataregarding the habits or interests of the user and can be furtherutilized by the system to generate unique and individualized content tothe user.

A unique feature of one embodiment of the methods and systems detailedherein is the generation of unique content upon the aggregation of atotal number of users within a particular system, in which the group asa whole is responsible for meeting a threshold to access content,digital offers, or combinations thereof.

For example, Home Team has announced that they are providing a uniquedigital offer to all fans in the stadium if x number of fans are all onthe system at a given moment. Home Team has a total of 10,000 fans inattendance and the unique digital offer is being triggered upon meetinga threshold of 1,000 fans all being on the system at a given moment.Upon meeting the threshold, a unique digital offer is provided. Thiswould be operable, as detailed in FIG. 6.

A first user, and a plurality of users would use a user device (14 a) toscan a tag (16 a) having a MRC (17 a) therein, for example on a seatback(210). Scanning by the user device (14 a) engages theredirect/identification server (302), and to the interface server (306).Here, the target determination process (644) includes a rule that isdefined by requiring a counting of a total of 1,000 user devices beingactive on the system at a given moment. Accordingly, a counting module(602), must receive and manage the number of user devices active on thesystem at a given moment from the interface server (306). The thresholdbeing the 1,000 active users, provides that the database is storing aparticular target, which is the release of a special coupon for a freehotdog to all active users. The counting module receives and tracks thenumber of active users as it increases or decreases. For example, thecounting module may also populate or display the total number of users,either on the user device (14 a) within the fan portal, on the jumboscreen, or on a video display. Upon meeting of the 1,000 active userthreshold, the target determination process receives confirmation fromthe interface server to retrieve the target, being the free hotdog, andthen pushes that information form the database to the interface server(306), through the redirect/identification server (302) to the userdevice (14 a).

The venue can then set this particular rule, wherein additional users,who later access the system may also receive the offer, or only userswithin x number of minutes receive the offer, or any other rule asdetermined by the proprietor. The free hotdog thus is provided through aredirect to a new page on the user device or is pushed to the user,through a Web app or through a socket, as non-limiting options. The usercan then use the free hotdog offer. As the system is enabled, the systemwould know the seat of each user awarded with the 1,000 hotdogs andcould automatically deliver those hotdogs to the seats of those users,as it would have the tag ID corresponding to each seat. Otherwise, theuser could request the hotdog be delivered, and have it brought to theuser's seat by accessing this option through the fan portal, or the usercould walk to a concession stand to redeem the free hotdog using thedigital offer delivered to the user device.

FIG. 7 details this in a flow diagram (700), with the first step (702)being to scan the tag. The user is authenticated, verified (704), asdetailed in FIGS. 4 and 5. As each user ID passes through the interfaceserver, a request is received at the target determination process (706)as to what rule to apply. Here, the target determination process sets arule that at 1,000 users online, a free hotdog will be provided to those1,000 users. When less than 1,000 users are online, then the targetdetermination process (706) receives a redirect target from the databaseand sends this back through the interface server andredirect/identification server to load on the user device (14 a) a homepage or other target. The interface server then looks for the unique IDto count the user (708). However, upon the meeting of an occurrence of atrigger or threshold (710), and as further detailed by FIG. 7, thetarget determination process of the interface server determines that therule of 1,000 users online is met (712) and triggers the release of thepre-loaded content. Thus, the target determination process receives thetarget from the database (714), and whatever target material waspredetermined. The interface server then instructs theredirect/identification server where to direct the user (716), here theuser is redirected to a URL end point, pushed data, socket pushed data,or provided information through a Web app (718), which here is thedigital offer for the free hotdog.

Instead of a plurality of users meeting a threshold, a single user mayneed to meet some threshold, for example, scanning a tag at tenlocations within the city, as shown in FIG. 11. Joe user scans one tageach day for ten days (i.e., the tag at location [1101], the tag atlocation [1102] and the tag at location [1103]), and on the tenth day,upon meeting the requirement threshold, the unique content or digitaloffer is delivered. Thus, a new movie pilot is released, and the specialdigital offer is the first 500 users to complete 10 scans receives aspecial viewing of the movie. Joe User completes the task and is one ofthe first 500 users and thus receives the special digital offer. Theseelements are defined within the system described herein.

Upon the occurrence of scanning into the system, the user and a uniqueID are determined. The system can determine the total number of users onthe system at a given time, i.e., the number of users who have scannedthe tag (16 a) within a given time period. In certain embodiments, thethreshold may be defined as a total number of users who have scanned atag (16 a) during an event, and not simply who are presently online at agiven moment. Thus, as in FIG. 2, the countdown (216) may refer to thetotal number of scans from unique user IDs at the venue during aparticular event. Even if individuals are not currently on a userdevice, the act of scanning the tag (16 a) is sufficient for thepurposes of unlocking the unique digital offer (214) or content.

In other embodiments, the countdown (216) and the threshold arereferring not simply to a single venue, but to the system as a wholeacross all venues and/or events, or proprietors who utilize the system.In such an embodiment, a plurality of tags at one venue or location anda plurality of tags at N number of other venues or locations arecombined together. Thus, while a single venue may only have 10,000unique tags, across the entire system, there may be 10,000,000 uniquetags. This provides a much larger pool of users from which to access forgenerating the unique offer (214). In certain embodiments, once on thesystem, a user may need to engage with a particular element, aparticular offer, or perform some action so as to be counted for theunique offer (214).

For example, a new movie is coming out in the BEST MOVIE EVER series.The prior movies in the BEST MOVIE EVER series generated more than 1billion in ticket sales and there is already interest in the nextto-be-released film in the series. A special movie trailer is beingadvertised, but to date only teaser shots of a few seconds are released.Upon generating 1,000,000 unique users to the system, the full movietrailer will be released. By scanning a tag (16 a) a user and the userID are engaged to the system and count as one of the 1,000,000 uniqueusers. A threshold is set for 1,000,000 unique users in a time period t,which is set for three hours on a given day. Thus, unique IDs that arecounted as entered into the system before that time period t and afterthat time period t will not count. Only those unique IDs on the systemduring the given time period t will count toward the n number.

Alternatively, the movie trailer will be released if 500,000 unique userIDs are online and active within the system at any point during timeperiod t. The system can track and identify both counting numbers andupon meeting one of the thresholds, release the full movie trailer. Thefull release movie trailer may be only provided to those users whoengaged in the system or can be released publicly at that point. Themethod here relates to communal interest in unlocking content. Theproprietor, in this example, the movie company, may provide furtherdigital offers to those users who participated, and, such digital offerscan be modified based on the behavior and characteristics of the uniquedigital offer as it relates to the unique ID (i.e., the unique digitaloffer is shared on a social media and viewed 1 time as compared to asocial media that is viewed 1,000,000 times). Such shares havesignificantly different value and thus the digital offer can be modifiedaccordingly.

FIG. 8 is a block diagram illustrating a further embodiment of thesystem (800). In this embodiment, the feature is determining whether auser is a new user or a returning user. This is important as a new usercan claim a specific digital offer, but a returning user cannot. Thisway, when a specific offer is provided, a user can only obtain the offeronce. Thus, following the logic of the prior figures, following a scanof the tag (16 a) with the user device (14 a), the user is redirected toa tag URL that is uniquely encoded to the tag (16 a). Theredirect/identification server (302) receives the tag URL request checksfor a manifest and unique ID and if located, informs the interfaceserver (306) whether the user device (14 a) is new or a returning deviceinto the system (10). In this embodiment, the interface server (306)includes a database (308) of unique IDs. If the unique ID is determinedto be a returning user, for the purpose of claiming the digital offer,then that user is denied access to the digital offer to prevent the userfrom redeeming multiple digital offers. If the user is new and does nothave a unique ID on his user device, the process of FIG. 4 is followedto generate the same. Otherwise, if the unique ID is not new, but hasnot claimed the digital offer, the new user and returning, but unclaimeduser, now claim the digital offer. The target determination process(844) determines what content to display based upon data received fromthe redirect/identification server (302), and the target determinationprocess (844) communicates with the analytics portal (46), and theanalytics database (66), in view of the unique ID (22 a) to return atarget (807) (FIG. 6) through the interface server andredirect/identification server to the user device (14 a). Notably, allof this information is stored in a database corresponding to the uniqueID, so as to create a profile and information related to the user.

By including a check for the unique ID, two aspects occur. One, there isa confirmation that a single device is not scanning multiple tags tounlock special content multiple times. And two, it allows for each ofthe unique users to be counted and to be provided with the uniquecontent upon its release.

As part of this process, the user could be prompted to input personalinformation (38) (FIG. 9) in exchange for the digital offer. Theprovided information could be stored in an analytics database (66) ofthe analytics portal (46). The analytics portal (46) may perform anumber of tasks, including access to the unique ID database to retrieveinformation related to that particular unique ID. This can be performedon a multi-level server and database system as is known in the art.Thus, data can be stored in one or more databases and can be retrievedto allow for mining of data or to provide different data to one userover another based on the data within the portal. Thus, these databasesretain data from past user interactions, including interactions assignedto individual user and/or interactions of all users who have scannedmachine-readable code (17 a).

Turning to FIG. 9, and a flow diagram (1000) of FIG. 10. These examplesdefine variations of rules can be implemented on the system to deliverdynamic content. FIG. 9 details one such embodiment, with a flow diagram(1000) depicted in FIG. 10. Additional examples and iterations describedin further detail. FIG. 9 provides a first step (902) that a user device(14 a) scans a tag (16 a) on a seat (208). Following a scan of the tag(16 a) with the user device (14 a), the user is redirected to a tag URLthat is uniquely encoded to the specific tag (16 a) through step (904).The redirect/identification server (302) receives the tag URL request,checks for a manifest with a unique ID on the user device and informsthe interface server (306) and determines the status (new or not new) ofthe user device (14 a) to the system (900). By checking for a manifestand a unique ID on the user device and correlating it with the unique IDstored in the database a confirmation can be made of a new (34) orreturning user (36). If the user is new, a new unique ID is generated(906) by the system and stored in the database and on the user device.

The interface server (306) includes a database (308) of URLs containingunique certificates used to issue digital wallet passes. If the user isdetermined to be a returning user (36), the interface server confirmsthat the unique ID located on the user device matches the unique ID inthe database. If the user is a new (34) user, the system obtains amanifest with a unique ID and sends it to the user device (steps [406]and [408] from FIG. 4), and records the same within the database. Atthis point, the user is confirmed with an existing unique ID (22 a) orpossesses a new unique ID, in either case, the certificate used to issuea digital wallet pass being specific to that user device (14 a).

Subsequently, the unique ID being confirmed or generated, the targetdetermination process (844) determines what content to display basedupon data received from the redirect/identification server (302) in step(908), and the target determination process (844) is told what to showthe end user (910). The interface server and the target determinationprocess (844) further check for dynamic rules and directs back to theserver (912). The redirect/identification server sends the end user tothe redirect URL directed by the interface server (914). However, whilecontent is provided, a trigger then occurs (918). The occurrence of atrigger, as defined in the several examples herein, then generates a newtarget. Accordingly, the interface server determines the new target todisplay based upon the trigger occurrence (920). The process may repeatas additional occurrences of triggers are repeated to provide newtargets (922).

As part of this process, a step (916) may include that the user isprompted to input unique identifying information (54) (FIG. 6) into thesystem (10), which allows for better analytic information on the userdevice (14 a). The provided information could be stored in an analyticsdatabase (66) of the analytics portal (46) or in a primary database(308) among a variety of storage options.

Therefore, a target that was previously provided can actually bemodified by the occurrence of a trigger. For example, the digital coupon(32), based upon a live trigger, or based upon the actions taken by auser. For example, the trigger/outcome occurs (68), may be that a hometeam wins a game. Upon the occurrence of the trigger, the target oroffer, which was prepopulated within the database, a coupon can bemodified. Thus, the digital offer/target (32) first provided for a freedrink with an order of a slice of pizza can be changed through thetarget determination process (844) upon any rule being met, butspecifically here upon a trigger event. Thus, upon the occurrence of thetrigger (68), the digital offer (32) now provides a free drink and saladwith the order of a slice of pizza.

Another example of a trigger (68) may include: making donation, making awager, playing a game within the system (10), a predetermined lottery,the purchase of an item within the system, the purchase of an itemoutside of the system (10), but tracked via an outside API that connectsto the system (10). Because of the unique ID, we can track and identifyeach user device (14 a) and allow for customized communication basedupon the occurrence of a trigger (68).

In another embodiment, following a scan of the tag (16 a) with the userdevice (14 a), the unique user ID is able to communicate with otherunique user ID's currently on the system (10) via push notifications,via a chat link, or via a socket notification all within the fan portalon the user device (14 a). Because the MRCs (17 a) are uniquely coded toa particular seat, section or other fixed location, a user is able tocommunicate with other users in the same row, section, venue or otherlocation that is part of the system, without having access to the otheruser's unique identifying information such as cell phone number, e-mailaddress or social media username. Users would have the option ofreceiving communications from other users based on certain parameterssuch as, receive communications from users in my same row, users in mysame section, users from the entire venue or alternatively, not toreceive any communications.

In a typical embodiment, remotely updatable machine-readable codeprogramming provides an ability for individuals to download digitaloffers directly to their user devices and transfer the digital offer toother user devices. In a typical embodiment, once the individualtransfers the digital offer to a predefined number of user devices, theincentivized offer increases. The system uses the unique ID stored in amanifest on the user device and in a database on the server; therefore,this digital offer is now unique to the user device on which themanifest with the unique ID is stored and must be in order to track thesharing of the digital offer. If the individual transfers the digitaloffer from his/her user device to, for example, five other communicationdevices within a fixed time period such as, for example, a week, thedigital offer automatically upgrades from 10% to 20% off at the localretail store. This capability offers further incentive for individualsto transfer their digital offers to family and friends so that they willreceive greater discounts. Also, this capability will allow proprietorssuch as brands and retailers to watch their promotion go viral from afirst point of download to various locations where the digital offersare transferred between various user devices. These digital offers couldalso be shared and tracked via NFC, MMS, Text Message, social media suchas Facebook, Twitter, Snapchat, etc. Digital offers could be browserbased or stored into user's digital wallet located on his/her userdevice.

In a further example, BW Films is releasing a new motion picturetrailer. BW Films wants the initial trailer to be viewed by at least10,000 viewers on the initial launch and is marketing the film tocollege students. ZY University is hosting a football game at the campusstadium. As described more fully in FIG. 2 and FIG. 4, each seat in thestadium has a tag (16 a) installed on the armrest and each tag containsa MRC that is uniquely coded to the system via a tag ID. When the fansarrive at the stadium, each fan who wants to interact with the systemscans the tag on his or her armrest. Once scanned, method 400 isexecuted. The redirect/identification server can be programmed withcertain rules. For example, a rule could be if a user device does notrescan the tag within thirty minutes, or if the user does not interactwith any of the redirect URLs the interface server sends to the userdevice within a thirty-minute time period, that user device may becategorized as inactive and removed from the count of total number ofuser devices currently active on the system. A counting mechanism (FIG.6, 602) can be utilized with any of the embodiments to track and accountfor any rule or metric that requires some form of tabulation of users,whether a total or active, as non-limiting examples of counting. Oncethe redirect/identification server has verified that there are 10,000unique and active user devices on the system, it directs the interfaceserver to deliver a unique redirect URL to each user device that willallow the user to view the motion picture trailer.

In another example, BW Films wishes to reach a larger market to launch anew motion picture trailer. BW Films would like a total of 500,000viewers with a minimum of 5,000 viewers in each of ten venues. BW Filmsknows that Saturday is traditionally game day for college football. Asfans arrive at the campus stadium where tags are installed on thearmrests of the seats, the fans scan the tags with their user devicesand method 400 is executed. The redirect/identification server continuesto tally user information, via the counting mechanisms described in FIG.4, FIG. 5, and FIG. 6 until each parameter set by BW Films is met.Therefore, when the redirect/identification server knows that each ofthe ten venues designated by BW Films has 5,000 unique and active usersand that there are a total of at least 500,000 unique and active userson the system, the redirect/identification server will direct theinterface server to deliver a unique redirect URL to each user's deviceso that the user can view the film trailer. Alternatively, the interfaceserver can tally the number of unique user devices currently on thesystem rather than the tally being completed by theredirect/identification server.

In another example, tags are installed in hotel rooms throughout thecountry. WS Airlines would like to offer a flash sale on air travel andsets the parameter that there must be 10,000 unique users on the systemat one time in order for the digital discount offer to launch. When auser enters his hotel room, the user scans the tag with the tag that isinstalled in the user's hotel room and method (400) is executed. Oncethe redirect/identification server has tallied that the number of uniqueusers has reached the minimum threshold set by WS Airlines, theredirect/identification server directs the interface server to deliver atarget, i.e., a digital offer for the flash sale. The digital offer canbe a unique discount code for each user, a single discount code for allusers, a digital or mobile wallet offer that can be added to the userdevice, pushed to the user device, sent through a socket, updated in aWeb app, or the user can be sent a unique redirect URL.

In another example, N & N Candy is launching a new flavor of candy bar.The marketing campaign consists of a video advertisement and a digitaloffer for a free candy bar. N & N sets the parameters that this campaignwill be launched on college campus when the unique number of users oneach campus reaches 50,000. Each dorm room on the college campuscontains a tag. The tag contains a tag ID that is coded in the system toidentify that it is located on a particular college campus. Optionally,the tag ID can also be part of a tag grouping. When the student entershis dorm room, he uses his user device to scan the tag which executesmethod 400. In this instance, the counting mechanisms described in FIG.4, FIG. 5, and FIG. 6 not only counts user is new or existing, but thecount also tracks the university campus on which the MRC is locatedbecause each tag ID is part of a tag grouping for a specific campus. Theredirect/identification server tallies the number of unique and activeusers at each college campus location. Once the number of unique andactive users at any one location exceeds the number specified by N & NCandy, the redirect/identification server directs the interface serverto deliver a unique redirect URL to the user device which allows theuser to watch the video advertisement on his user device and theinterface server also delivers a digital offer for a free candy bar. Thedigital offer can be in the form of unique discount code for each user,a single discount code for all users, a unique digital or mobile walletoffer that can be added to the user's device or the same digital ormobile wallet offer that can be added to all user devices. In thisexample, the users at ZY University may meet the minimum threshold setby N & N Candy within one hour of the launch of the marketing campaignand thus be given access to the video content and free candy bar offerwithin one hour. However, the users at BA University may not meet theminimum threshold set by N & N Candy for several days and therefore, theusers at BA University will receive access to the video content and freecandy bar offer several days after the users at ZY University receivetheir offer.

In another example, a musical group would like to provide their fanswith an opportunity to download the group's latest single. The group isperforming in a venue that has a tag installed on the armrest of eachseat and each tag contains an MRC that is uniquely coded to the systemvia a tag ID. The group is also live streaming the event over theinternet and the online production of the performance will display a QRor similar MRC in the bottom corner of the video feed. The group hasdecided that they will release the single when the total number ofunique and active viewers reaches 100,000 users regardless of thelocation of the user device. Users at the venue scan the tag with theiruser device which executes method (400). Likewise, users viewing theconcert's live stream can scan the QR code that appears in the broadcastwith their user device which also executes method (400). Once the totalaggregate number of unique users meets the minimum threshold set by themusical group, the redirect/identification server directs the interfaceserver to deliver a unique redirect URL to each user device allowing theuser device to download the musical group's latest signal.

While counting of a plurality of users is important for mass marketing,in certain embodiments, individualized marketing is more important.Thus, in a further example, a user must scan a certain number of tags inorder to unlock specific digital content or offers. In this example, asshown in FIG. 11, tags are placed throughout one location or in multiplelocations (i.e., a bus bench [1101], a coffee shop [1102], or abillboard [1103]). However, this configuration could also work for amuseum with tags at multiple exhibits, a shopping mall with tags atmultiple stores, multiple tags placed throughout a particular town orcity at certain establishments in that town or city or multiple tagsplaced at particular locations throughout a larger geographical area.For purposes of the example, the tags have been placed at restaurantsthroughout Fort Worth, Tex. Stockyards Rodeo wishes to launch amarketing campaign where they provide a mobile or digital offer ofbuy-one, get-one-free tickets to users if the user has frequented acertain number of restaurants in the Fort Worth area. Stockyards has setthe parameter (i.e., rule) that users must visit four restaurants inorder to unlock the digital offer. When a user arrives at therestaurant, he uses his user device to scan the tag that may be mountednext to the door or the restaurant, in the lobby of the restaurant, orat a particular table in the restaurant, which executes method (400). Ifthe user is new, the identification server notes the device, location,date, and time of the scan and creates a new user/device ID record forthis campaign. If the user is existing, the server retrieves the user'sexisting user/device ID record for this campaign, notes the location,date and time of the scan and updates the user/device ID record toreflect the total number of scans. This process is repeated each timethe user scans a tag at a restaurant in Fort Worth until the user meetsthe parameter set by Stockyards to unlock the digital offer, in thisinstance, the user must visit four restaurants. Once the user/device IDrecord for this campaign meets the parameter set by Stockyards, theredirect/identification ID server directs the interface server todeliver a unique redirect URL or digital offer to the user device forbuy-one get-one-free tickets at Stockyards.

In certain embodiments, the system may be utilized in conjunction with adigital wallet or wagering wallet for wagering. In the event of awagering component, users would be able to scan the tag with the userdevice and be taken to a live wagering portal, which could be browserbased or in the form of a cloud or locally based mobile application,including a progressive Web app. Using the system's analytics portal,the user would be able to see their past wagers across the entire systemand place their wager utilizing a digital wallet solution such as ApplePay or Google Wallet, or through traditional payment methods. All of theinteractivity and wager-based actions will be facilitated without theneed for the user to create a traditional user profile, unless sorequired by law. This same wagering configuration could be utilized tooffer “brand wagers” wherein the prize given to the user is a physicalitem given to the user such as a promotional item from a team sponsor ora digital reward which can be downloaded or emailed to the user'sdevice.

Fan engagement at sports venues often goes beyond the game itself. Whenthe moment arises, fans are often generous to causes that are supportedby their team, which may be provided to nonprofit organizations.Therefore, in a venue, the team may request support of one or morecharities, and the platform could allow for the ability to donate moneyin real time directly from their venue seat via the NFC and/or MRC. Forexample, if the donation were to Salvation Army, the user would, eitherwith or without prompting from the venue multimedia display system orjumbo screen, scan their tag and be prompted to donate money eitherusing their digital wallet or traditional payment methods. In keepingwith the earlier claims, the system would allow proprietors to deployvarious customizable donation templates to every seat, row, or sectionif desired. Additionally, after the donation transaction is complete,the user could be offered a physical or digital reward that could beused inside or outside of the venue. Indeed, the benefit of the systemis that the user device contains a unique ID stored in a manifest thatis indicated in the system. Accordingly, this allows the system toidentify a user device corresponding to a particular user ID as donatinga certain dollar amount. The system can be prepopulated with “rewards”or incentives to donate or reach a cause.

For example, a cause may be for a single section of a venue to raise$100 (i.e., 224 from FIG. 2). All donations originating from tag withinthe particular section can then be aggregated to determine if thesection reached the $100 donation goal, or if a certain percentage ofthe section participated in reaching the goal. Accordingly, if there are200 people in the section, a donation of an average of 500 would besufficient to hit the goal. The system can then populate a predetermineddigital or physical reward, i.e., a coupon or some other offer that canbe used at the venue, or some other tangible or intangible reward. Thesystem can go one step further as it can quickly tabulate the donationsand, in real time, the system can allow sections to compete with oneanother. Thus, section 1 (i.e., 224 from FIG. 2) could “race” section 2(i.e., 226 from FIG. 2), to reach a donation goal. This allows forgamification within the system based upon the use of tags that areprovided in a venue or location.

Embodiments may also allow for real time data/polling of eventattendees, i.e., voting for your favorite player, predicted outcome ofthe game, predicted score, games displayed on a jumbo screen, real-timeevents/outcomes at the stadium, etc. However, the real-time polling isenabled by the individualized nature of both the user device and also ofthe tag. For example, where only one of the user devices or the tags isunique, it is impossible to identify both the user and also a populationof similar users. If a section of a stadium is competing against anothersection, we need to have each user device connect to a tag in theirparticular section, via a tag ID grouping, and then participate as agroup to reaching the offer threshold. If the group element is missing,such “sectional” competition would not be possible.

While the group may participate together, because of the unique ID,individual user rewards can be provided, for example, as a user makes alarger donation, that user is provided with a larger reward than anotheruser from the winning section. Because the unique ID stored in amanifest on a user device allows for tracking of actions, i.e., thedonation by the user, individual rewards can be provided to that user,corresponding to that particular unique ID.

All of these actions provide opportunities for the system to captureuser data. When the plurality of tags (16 a) is scanned with the userdevices (14 a), analytical data is collected. The analytical data maybe, for example, date, time, GPS location of a tag, GPS location of auser device (14 a) when it scanned a tag, the type of user device usedto scan a tag, orientation of a user device when a machine-readable codewas scanned, and type of operating system on a user device that scannedthe tag. The exemplary method and system couple the collected analyticaldata from the physical scanning of the plurality of tags (16 a) withdata collected once the individual is directed to the target. In atypical embodiment, the data may be, for example, time spent on a Webpage, purchases made, IP address, personal information input by theuser, and products viewed. Such data is of high value to, for example,advertisers, team owners, and venue owners as it provides a largeinsight into consumers purchasing and Web browsing habits.

The user data can remain anonymous to a large extent, as it is collectedbased upon the user device scanning a tag and not dependent on the userlogging into the system. Therefore, data does not need to be correlatedwith the actual identity of the person controlling the user device. Itis immaterial whether the user is male or female, or young or old,instead it is the particular set of data that creates a picture andcertain mobile offers or content can be provided based upon that data,and then modified based upon the occurrence of one or more actions, suchas donations as above, or other purchases, or an outcome in an embeddedgame or task, or upon the outcome of the game at the venue, asnonlimiting examples.

Data can also be gathered outside of the system, for example, through anAPI connecting the system to a third-party server or database. Thebenefit of also utilizing user data that is gathered from outside ofsystem itself is that it provides data that might not otherwise begathered, while also offering an opportunity to “preset” content when auser scans the tag at their seat. Example 1: If event ticket providersuch as Ticketmaster®, provided data to the system's analytics portalrevealing that Joe purchased tickets to the football game to sit in seat1, row 1, while also providing data, known to Ticketmaster, such as thatJoe is a 32 year old male (data that is provided to Ticketmaster fromJoe when he creates his Ticketmaster account), because each tag in thesystem is uniquely encoded down to the individual seat or specificlocation via a tag ID, the analytics portal would have the ability to“preschedule” content that would appeal to a 32 year old male when Joetakes his seat at the game. This use case could be valuable formarketers looking to market to a particular subset of attendees, vs theentire stadium or venue. The data can be from more than just one eventas well. If Joe has previously purchased other tickets fromTicketmaster, that data may also be available and provides furtherdetails and information relevant to Joe, which can be used to providebetter content to Joe. If Joe only buys rock concert tickets, forexample, providing country music listings for new concerts would not bethe best targeted advertising for Joe—so modifying the content to thatof Joe's interests (rock concerts) provides greater value foradvertisers and also to Joe.

A machine learning component of the system would allow sports teams toprovide more relevant real-time offers to fans by customizing contentbased on user interaction. Example 2: If Joe scans his tag and is takento the team fan portal where he selects “buy merchandise”. 75% of thetime Joe purchases a shirt, but he never buys a hat, then the systemwould have the ability to adjust Joe's offerings in real time to showhim a larger selection of shirts, instead of hats, based off of his pastpurchasing and browsing habits. Alternatively, the system could use thisdata stored on Joe's purchasing habits to deliver a customized digitaloffer to Joe to entice him to buy merchandise that is not a shirt suchas a 25% discount if Joe buys a hat. This could be valuable toproprietors, teams, performers, promoters, or venues looking to sellitems from merchandise to food inside of the venue or based uponinventory considerations. The system has the ability to learn usercharacteristics from user input within various user portals mentionedabove (Web browsers, PWAs, etc.). This component would provide a userwith customized content based on their previous content interactionsinside of one venue, or interactions across the entire system network oftags. It would also allow said system to store user and/or the userdevice information in order to offer specialized incentives based onpast usage statistics. For example, the system may reward Joe forscanning the tag at his tenth straight baseball game by delivering anoffer for “team VIP” merchandise. Or the system could provide Joe anoffer for a hot dog, peanuts, or soda at a reduced rate based on hispurchase history or incentivize him to make a purchase with a digitaloffer, if he typically does not purchase food or beverages.

The benefit of the unique ID, in combination with the tag ID is that asingle tag, having its own tag ID, can be scanned by multiple userdevices, and each scan by a different device will have a differentunique ID. This allows proprietors such as venue owners, teams,universities, marketers, performers, promoters etc., to offerindividualized digital offers to every user device that scans a tag.Example 3: The system offers unique digital wallet certificates for eachuser upon scanning the tag, which means that if fifty users scan thesame tag with their user device, all fifty user devices willindividually have a unique record within the system database. Thus, asingle tag could be located in a centralized location and would stillallow for unique content (the digital offer) to any user who scannedthat tag. The system might deliver a different digital offer to eachuser so if Joe scans the tag, his digital offer might be for a halfprice soda at the concession stand, but if Joe's wife scans the same tagfrom a different user device, having a different unique ID stored in amanifest, her digital offer might be for a half price hamburger at theconcession stand. Likewise, the system will be able to track if a useractivated and redeemed his or her digital offer.

The system may offer “group passes” wherein the system could offer adigital offer that was only able to be issued to a predetermined numberof users. Thus, the first person, the first 5, the first 10, 25, 50,100, 500, 1000, 10,000, nth, person to scan the tag (and all numbers inbetween), may be included within a group. The distribution of such grouppasses and counting of executions of the system to a user device, can beused as a game or for other giveaway plans. It is common knowledge ofthe types of games where the “100th person to download wins a prize,” or“only the first 100 people can claim a prize if they buy or click now.”The ability to track these types of programming through the systemprovides a new way to manage such programs.

The system could also be implemented within a traditional mobileapplication or Web-based platform whereas the user would be offered theunique digital offer once they visit said application or URL address.Because of the individualized nature of the unique ID in the system, theunique digital offer can then be directly modified based upon chance,some data, or trigger occurring which allows the provider of that uniquedigital offer the opportunity to modify an offer. For example, an offeris for 10% off a pizza, but the offer becomes 25% off once the offer isshared with at least 2, 5, 10, 25, 50, n number of people, who alsodownload an offer. This allows tracking of who downloads an offer, howmany are tracked to a particular offer, and allows for modification andimprovement of an offer based on metrics related to sharing.

Another embodiment would be for a proprietor such as a retailer toprovide a digital offer in the form of real time discounts to users inspecific venues via the tags (16 a) upon the occurrence of a thresholdset by the retailer. For example, if the tags (16 a) inside of the venue(202) are linked to a specific retailer via a tag grouping orgeofencing, then that retailer could offer discounts in real time thatcould only be accessed by users inside of the venue (202) upon theoccurrence of meeting a threshold of interest in that particular offer.Here, the trigger event is that at least five people scan a tag relatedto a particular offer. The occurrence of a real time discount is atrigger, wherein the trigger executes a modification of a digital offeror of the content that is provided to the user device (14 a) as soon asthe at least five people scan the tag for that offer.

Embodiments of the invention also provide individuals an ability toestablish interactive communication via tags (16 a). In a typicalembodiment, the plurality of tags (16 a) can be programmed to performvarious designated actions such as, for example, an ability to downloada digital offer (e.g., a digital coupon) straight onto the user devices(14 a) which could be redeemed at a concession area or retail location.For example, the digital offer could be redeemed by the individuals uponperforming a transaction at a retail or concession area using, forexample, the NFC enabled user device. This provides proprietors such asconcession owners, retail owners, and advertisers an ability toimmediately see conversion rate of a digital offer that is issued (i.e.,100 coupons were scanned via the plurality of tags and 80 wereredeemed). These digital offers could be redeemed at retail locationsinside or outside of the venue. If the offer rate is lower than desired,the proprietor can increase the offer to improve the rate of use of theoffer.

The machine learning and custom content aspect of the system is notlimited to in-venue applications and can be utilized across multipleindustries such as rideshare vehicles, aircraft, ships, trains, hotelrooms, dorm rooms, vacation rentals, etc. The broad spectrum of theembodiments is to offer location based custom content solutions to userdevices.

In the case of hotels and collegiate dorm rooms, the system would becomprised of a plurality of uniquely encoded tags (16 a) placed insideof guest rooms whereas there is one NFC enabled and/or MRC tag per room,or one per guest/resident of said room. Each tag (16 a) would beconnected to system servers which would allow said tags to offerpredetermined content based on pre-supplied data points. In thecollegiate dorm use case, users would scan the tag (16 a) located withintheir room and be shown content based on various factors such as theirgender, education major, year of schooling, etc. The content on thesetags would also utilize data points and usage reports from the systemitself to better serve users with relevant content. These tags couldalso allow marketers, and the university at which they are deployed, tooffer incentives such as game tickets or retail store coupons, directlyto the students in their dorms via a digital offer or mobile walletoffer, while providing the option to provide the offers and content toonly select, or all, tags based on various analytics provided within thesystem. Tags would also allow students and hotel guest to offer realtime feedback on the system in the form of user submissions to conductlive polling procedures. This use case would provide a valuable platformfor universities, marketers, and hotel owners to offer customizedcontent to their guest on an individualized basis.

Another unique feature of the system is that the data that is collectedin order to provide content can be gathered system wide when a userscans one of the plurality of tags in any location. This feature wouldallow marketers to understand consumers characteristics more closelyfrom a location experience, and to provide the user relevant contentacross a multitude of markets. Example 4: If a tag is scanned by Joe ata football game in Arlington on a Sunday, and then a tag is scanned byJoe in a rideshare vehicle in Boston the following Wednesday, the systemwould understand that the user, Joe, was the same for both interactions,without Joe having to log into the system, and display contentaccordingly based on data provided from the analytics portal. This isbecause the system knows the user, Joe, because of the unique ID storedin either on the manifest on the user device or on the server, or both.By scanning a tag, the system can also upload data to generate moreinformation Joe and his activities and interests, so as to providebetter content to Joe through the content.

The step of collecting user data associated with the user may alsoinclude the step of receiving in-venue metrics via an in-venue metricsAPI (50). This API (50) may enable information about the user to begathered based upon purchases of tickets (past and present), purchasesof food, merchandise, and other goods and services from the venue. Thestep of collecting user data associated with the user may also includethe step of receiving third-party metrics via a third party metrics API(52). This third party metrics API (52) may enable information about theuser to be gathered from third parties who participate in a sharedprogram, or who sell or otherwise provide marketing information,demographics, and other data about the user. The step of collecting userdata associated with the user may also include the step of receivinginformation from other data forms available to the system.

Finally, as ticketing is a key feature of many of the embodiments, thestep of collecting user data associated with the user may also includethe step of receiving information from ticket brokerage metrics via aticket brokerage metrics API (56). These metrics may include informationgathered by the ticket brokers who sell tickets at the venue (202) (inFIG. 2), and may include a wide range of marketing data, not only aboutticket purchases made, but also related information about the user.

Rolling offers may also be desirable. For example, a restaurant at asporting venue may want to discount food (so none is wasted at the endof the game) and selling food for discount when a specific time point inthe game or event is reached. This allows for real-time feedback withinthe event and within the system of inventory, wherein price or an offercan be modified based on the particular inventory. An advertisement orcoupon can be generated as mobile content in real time to users on thesystem to incentivize such consumption. For purposes of thisapplication, the terms “real time” and “real-time” means anyinteractions that are provided within ten seconds of a triggeroccurring, or longer, as determined by the proprietor, but not longerthan 60 seconds after the occurrence of a trigger occurring.

Referring back to FIG. 3, the infrastructure detailed therein isexemplary, dividing processing between at least two servers (e.g.,redirect/identification server [302] and interface server [306]), butembodiments are not so limited. The numbers and types of servers andsoftware may be scaled up, down, and distributed according to platform(20) demands/needs. Furthermore, more than one virtual machine may runon a single computer and a computer/virtual machine may run more thanone type of server software (e.g., the software that performs a service,e.g., Web service, application service, and the like). Thus, in someinstances platform (20) may include one computer for all processingdemands, and in other instances platform (20) may include several,hundreds, or even more computers to meet processing demands.Additionally, hardware, software, and firmware may be included in orremoved from platform (20) to increase functionality, storage, and thelike as needed/desired.

Administrator device (12), which is shown in FIG. 1, may be any type ofcomputer such as a laptop computer, desktop computer, tablet, and thelike. Similarly, user device (14 a or 14 b) may be any type ofprocessing device such as a handheld computer (e.g., phone, smartphone,tablet, personal digital assistant), wearable computer (e.g., watch,glasses), or portable computers (e.g., laptop, netbooks). Scanning ofthe tag (16 a, 16 b) from the user device (14 a or 14 b) is performedthrough near-field communication (NFC) or use of a camera on the userdevice (14 a or 14 b) to scan the visible quick response code (QR code).Administrator device (12) and user devices (14 a or 14 b) typicallyinclude a browser application to facilitate communications with one ormore servers among other things.

Administrator device (12), user devices (14 a, 14 b), and servers (e.g.,302, 306, 310, 312, 320, 322, and 324) may each be a general-purposecomputer. Thus, each computer includes the appropriate hardware,firmware, and software to enable the computer to function as intendedand as needed to implement features detailed herein. For example, ageneral purpose computer may include, without limitation, a chipset,processor, memory, storage, graphics subsystem, and applications. Thechipset may provide communication among the processor, memory, storage,graphics subsystem, and applications. The processor may be anyprocessing unit, processor, or instruction set computers or processorsas is known in the art. For example, the processor may be an instructionset based computer or processor (e.g., x86 instruction set compatibleprocessor), dual/multicore processors, dual/multicore mobile processors,or any other microprocessing or central processing unit (CPU). Likewise,the memory may be any suitable memory device such as Random AccessMemory (RAM), Dynamic Random-Access memory (DRAM), or Static RAM (SRAM),without limitation. The processor together with at least the memory mayimplement system and application software including instructions,including methods, disclosed herein. Examples of suitable storageincludes magnetic disk drives, optical disk drives, tape drives, aninternal storage device, an attached storage device, flash memory, harddrives, and/or solid-state drives (SSD), although embodiments are not solimited.

In an embodiment, servers (e.g., 302, 306, 310, 312, 320, 322, an/or324) may include database server functionality to manage database (308)or another database. Although not shown, infrastructure variations mayallow for database (308) to have a dedicated database server machine.Database (308) and any other database may be any suitable database suchas hierarchical, network, relational, object-oriented, multimodal,nonrelational, self-driving, intelligent, and/or cloud based to name afew examples. Although a single database (308) is shown in FIG. 3, inembodiments database (308) may comprise more than one database, the morethan one database may be distributed across many locations, and data maybe redundantly recorded in the more than one database. Furthermore, datamay be stored in blocks that are part of a chronological blockchain(314) and may be dispersed across a decentralized distributed ledger.Blocks of data in a blockchain are linked in such a way that tamperingwith one block breaks the chain. Thus, digital data stored in ablockchain is verifiable with an elevated level of integrity. Therefore,the database (308) may also be a distributed database system, utilizingblockchain (e.g., 314) to provide for storage of NFTs or the likerelated to the system. As with any distributed database, the number ofdatabases and particular nature of the blockchain storage is dependenton the particular exchange or blockchain utilized for the NFT as onenon-limiting example. The use of a distributed database system is wellknown and the storage of an NFT or the like requires the use of suchsystems. Geofence (316) and Time (318) may be software services providedby the platform (20). These services (316, 318) may be executed by anyor all of the computing machines, virtual or otherwise, found on theplatform (20). These services may use data from one or more user devices(14 a, 14 b) and other data sources to provide their intendedfunctionality as is known in the art.

It will be appreciated that the embodiments and illustrations describedherein are provided by way of example, and that the present invention isnot limited to what has been particularly disclosed. Rather, the scopeof the present invention includes both combinations and sub combinationsof the various features described above, as well as variations andmodifications thereof that would occur to persons skilled in the artupon reading the forgoing description and that are not disclosed in theprior art. Therefore, the various systems and methods may include one orall of the limitations of an embodiment, be performed in any order, ormay combine limitations from different embodiments, as would beunderstood by those implementing the various methods and systemsdetailed herein.

What is claimed is:
 1. A method for delivering dynamic content to a userdevice via a machine-readable code comprising: a. in response toscanning a tag comprising the machine-readable code, receiving a requestfrom a user device and detecting the presence of a manifest comprising aunique ID, wherein if no unique ID is present, creating a unique ID andassociating a record with the unique ID within a database; b. detectingfrom the tag a tag ID and determining: i. whether a venue existscorresponding to the tag ID; and ii. whether an event is in progresscorresponding to the tag ID; c. redirecting to a global default targetif no venue exists or no event is in progress, and determining if a tagID is grouped where the venue exists and an event is in progress; d.counting, via a counting mechanism, the total number of unique IDsscanning a tag within the venue, displaying on a display associated withthe user device, the venue, or both, the counting of the countingmechanism, and determining, via the counting mechanism, whether athreshold number of unique IDs have scanned a tag; e. upon meeting thethreshold number, in response to the detecting from the tag ID,obtaining tag ID group information and associating the tag ID with theunique ID; f. associating the unique ID and a unique ID record with thetag ID and redirecting a user to an appropriate target; and g. providinga first target to the user device when the threshold number is unmet,the first target customized based on the venue, the event, the tag ID,the tag ID group information, the unique ID, or combinations thereof,and redirecting the user device to the target upon meeting the thresholdnumber wherein the redirected user device corresponds with a unique IDcounted by the counting mechanism.
 2. The method of claim 1 wherein thethreshold number is selected from the group consisting of: a totalnumber of unique users on a system at a time t, the total number ofunique users accessing a system after a time t, x number of scanscorresponding to a unique ID and x number of tags, and combinationsthereof.
 3. The method of claim 2 wherein the total number of uniqueusers on the system at a time t is greater than 1,000.
 4. The method ofclaim 2 wherein the total number of unique users on the system after atime t is greater than 1,000.
 5. The method of claim 1 whereinredirecting the user device to a new target is redirected through a pushnotification.
 6. The method of claim 1 wherein the machine-readable codeis selected from the group consisting of: a barcode, a quick response(QR) code, a near-field communication (NFC) code, a radio-frequencyidentification (RFID) code, and combinations thereof.
 7. The method ofclaim 1 wherein the target is stored within a database and isautomatically redirected upon the occurrence of the event.
 8. The methodof claim 7 wherein the target is selected from the group consisting of:a digital offer and an advertisement.